Yes.
In your cold fusion code, expire a cookie. In your javascript code, check to
see if the cookie exists. If it DOES exist, that means the CF code was not
executed on the load, and you can do an automatic javascript refresh. Then
in the javascript code, set the cookie again.
It's a simple hack
The forwarding works fine as long as I pass all the url variables I need.
-Original Message-
From: Coldfusion [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 13, 2006 6:43 PM
To: CF-Community
Subject: RE: JS history.go
If you are uploading a document or any update and want to show
No-caching on what? The cfquery? Meta?
-Original Message-
From: Charlie Griefer [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 13, 2006 6:49 PM
To: CF-Community
Subject: Re: JS history.go
to expand on that, 'history' is just that. it pulls from the browser's
PROTECTED]
Sent: Wednesday, September 13, 2006 6:43 PM
To: CF-Community
Subject: RE: JS history.go
If you are uploading a document or any update and want to show the new file,
why not just use the button To go to the page itself rather than using the
history. History is just that Previous data. Not new
t use the button
> To go to the page itself rather than using the history. History is just that
> Previous data. Not new data.
>
> -Original Message-
> From: SMR [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, September 13, 2006 6:37 PM
> To: CF-Community
> Subject: RE: J
, September 13, 2006 6:37 PM
To: CF-Community
Subject: RE: JS history.go
Yeah but it doesn't refresh when I go back.. Documents just uploaded don't
show up in the list unless I hit the IE refresh button..
-Original Message-
From: Robert Munn [mailto:[EMAIL PROTECTED]
Sent: Wednesday,
Yeah but it doesn't refresh when I go back.. Documents just uploaded don't
show up in the list unless I hit the IE refresh button..
-Original Message-
From: Robert Munn [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 13, 2006 6:11 PM
To: CF-Community
Subject: Re: JS histo
the challenge with refreshing the page is getting the browser to expire the
previous page. Have you tried using a META tag to mark the content expired?
Something like this:
<*META* HTTP-EQUIV="*expires*" CONTENT="#now()#">
On 9/13/06, SMR <[EMAIL PROTECTED]> wrote:
>
> anyone know how I can use t
