On Tuesday 09 Dec 2008, Phillip M. Vector wrote:
Personally, I would have your process first check to see if the process
is done already. If it is, then don't do it.
Yeah, fix the application, don't break the browser.
--
Tom Chiverton
Helping to advantageously restore front-end unique systems
Hey all,
Is there a way to detect the use of the browser back button?
I have an issue where I need to prevent a process from running if the
browser back button is used..
thanks in advance
sas
--
Scott Stewart
ColdFusion Developer
Office of Research Information Systems
Research amp; Economic
CFLOCATION. Never render a page when it's an action request; always
redirect to somewhere else that just renders (doesn't perform an
action).
cheers,
barneyb
On Tue, Dec 9, 2008 at 12:08 PM, Scott Stewart [EMAIL PROTECTED] wrote:
Hey all,
Is there a way to detect the use of the browser back
That doesn't make any sense Barney.
-Original Message-
From: Barney Boisvert [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 09, 2008 2:21 PM
To: cf-talk
Subject: Re: The infamous back button
CFLOCATION. Never render a page when it's an action request; always
redirect to somewhere
Scott Stewart wrote:
Hey all,
Is there a way to detect the use of the browser back button?
I have an issue where I need to prevent a process from running if the
browser back button is used..
thanks in advance
sas
No, not really.
You can structure your application to work correctly
Andy Matthews wrote:
That doesn't make any sense Barney.
If you have page A that collects data from an user which then calls page
B which process the data which then uses cflocation... to page C for
the display of the results. If the user presses the back button they
are sent back to page A
.
-Ryan
Andy Matthews wrote:
That doesn't make any sense Barney.
-Original Message-
From: Barney Boisvert [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 09, 2008 2:21 PM
To: cf-talk
Subject: Re: The infamous back button
CFLOCATION. Never render a page when it's an action request
).
cheers,
barneyb
On Tue, Dec 9, 2008 at 12:33 PM, Andy Matthews [EMAIL PROTECTED] wrote:
That doesn't make any sense Barney.
-Original Message-
From: Barney Boisvert [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 09, 2008 2:21 PM
To: cf-talk
Subject: Re: The infamous back button
Actually, no. It goes back to page B.
Ian Skinner wrote:
Andy Matthews wrote:
That doesn't make any sense Barney.
If you have page A that collects data from an user which then calls page
B which process the data which then uses cflocation... to page C for
the display of the results. If
Personally, I would have your process first check to see if the process
is done already. If it is, then don't do it.
Scott Stewart wrote:
Hey all,
Is there a way to detect the use of the browser back button?
I have an issue where I need to prevent a process from running if the
browser
Not if you use CFLOCATION or JavaScript location.href. After processing a form
(A) to an action on the server side (B), go ahead and 'relocate' to the next
view page (C) and the browser will have only (A) and (C) in its history. This
also helps prevent someone hitting F5 while on (C) and
If you have page A that collects data from an user which then calls page
B which process the data which then uses cflocation... to page C for
the display of the results. If the user presses the back button they
are sent back to page A bypassing page B's processing since the client
never
No. If you do a server-side redirect the browser won't put B in
history, only A and C. If you use a META tag or JS's window.location
you'll get B in history, but not with server-side.
On Tue, Dec 9, 2008 at 1:00 PM, Phillip M. Vector
[EMAIL PROTECTED] wrote:
Actually, no. It goes back to page
I realize that now. It seems wrong, but I guess it's right. :)
Justin Scott wrote:
If you have page A that collects data from an user which then calls page
B which process the data which then uses cflocation... to page C for
the display of the results. If the user presses the back button
have your process first check to see if the process
is done already. If it is, then don't do it.
Seconded.
Log the start time, stop time, and a random identifier each time a process runs.
(Can either store these in a shared scope, or in a file, depending on what
process does and what makes
Ah...that makes sense now. I already do that...
-Original Message-
From: Barney Boisvert [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 09, 2008 2:43 PM
To: cf-talk
Subject: Re: The infamous back button
Why not? That way every URL stored in the browser's history is a
safely
If you do a server-side redirect the browser won't put B in
history, only A and C. If you use a META tag or JS's window.location
you'll get B in history, but not with server-side.
Possibly getting into the realms of pedantry, because you're ultimately
correct, but server-side is a bit
Lately I've been doing stuff like that in a modal cfwindow. Takes the
back button right out of the picture.
On Tue, Dec 9, 2008 at 3:08 PM, Scott Stewart [EMAIL PROTECTED] wrote:
Hey all,
Is there a way to detect the use of the browser back button?
I have an issue where I need to prevent a
18 matches
Mail list logo
