Ryan,
>Well yeah, you use frames, theres lots of things that go out the
>window! (sorry, im anti frames, I never consider them)
Even without frames, it still doesn't work if people have multiple
windows/tabs open to your site. Considering I almost always have multiple
tabs open on a site, this so
Well yeah, you use frames, theres lots of things that go out the
window! (sorry, im anti frames, I never consider them)
And It just depends on if it matters if the page linking back to
itself makes a difference. If not, this is a whole lot better than
creating a uuid and hitting the db and all th
Ryan,
>
>http://localhost/mypage.cfm?foo=bar"; />
>
>
> Page was refreshed
>
> Page was not refreshed
>
>
>
There's a lot of instances where that logic isn't true. If you're site is
using frames or the user has multiple windows open, this logic fails. Also
as you stated, if a page links back
:03 AM
> To: CF-Talk
> Subject: RE: Trying this again w/o the suject hijack (determinig if the
> refresh button has been clicked)
>
> >Obviously... but what would you be comparing that to?
>
> You'd have to keep track of each UID that's been visited. You wouldn't ha
lto:[EMAIL PROTECTED]
Sent: Thursday, December 22, 2005 11:03 AM
To: CF-Talk
Subject: RE: Trying this again w/o the suject hijack (determinig if the
refresh button has been clicked)
>Obviously... but what would you be comparing that to?
You'd have to keep track of each UID that's been vis
ED]
Sent: Thursday, December 22, 2005 10:45 AM
To: CF-Talk
Subject: RE: Trying this again w/o the suject hijack (determinig if the
refresh button has been clicked)
Obviously... but what would you be comparing that to?
...:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.
Bobby Hartsfield
http://acodersl
>Obviously... but what would you be comparing that to?
You'd have to keep track of each UID that's been visited. You wouldn't have
to track the UIDs given out, just the ones visited. If a UID is discovered
that already exists, then the page must have been a refresh.
Like I said this very, very kl
this again w/o the suject hijack (determinig if the
refresh button has been clicked)
Bobby,
>Wouldn't the flaw be that the refresh would generate a new UID...
No. Because the UIDs would be in the links, so that would stay the same
between refreshes
Hi!
One other option could be to use cookies. When the user first comes to a
page you would detect for the cookie and set it if it is not already set.
If you want to keep a counter, just get the value and reset it in the cookie
(client side js would be best for that). The negative would be the
p
Bobby,
>Wouldn't the flaw be that the refresh would generate a new UID...
No. Because the UIDs would be in the links, so that would stay the same
between refreshes.
-Dan
~|
Find out how CFTicket can increase your company's c
bject: RE: Trying this again w/o the suject hijack (determinig if the
refresh button has been clicked)
Scott,
>Does anyone know of a way to programmatically determine if the browser's
>refresh button has been clicked?
There's really no way to do that. There's nothing that diffe
Scott,
>Does anyone know of a way to programmatically determine if the browser's
>refresh button has been clicked?
There's really no way to do that. There's nothing that differentiates a
"refresh" from a first time request. They both pass in the same header
information to the server.
Any kind of
> -Original Message-
> From: Scott Stewart [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, December 21, 2005 2:02 PM
> To: CF-Talk
> Subject: Trying this again w/o the suject hijack (determinig
> if the refresh button has been clicked)
>
> Does anyone know of a
Does anyone know of a way to programmatically determine if the browser's
refresh button has been clicked?
Scott A. Stewart
ColdFusion Developer
GNSI
11820 Parklawn Dr
Rockville, MD 20852
(301) 770-9610
-Original Message-
From: Scott Stewart [mailto:[EMAIL PROTECTED]
Sent: Wednesday,
14 matches
Mail list logo
