you wrote:
>This is incorrect. cflocation simply sends a HTTP 302 "Found" statuscode
>to the browser together with a Location header. How could the URL one
>sees in the browser possibly change if nothing was send to the browser?
This is my understanding:
Of course something is sent to the browser, but AFTER the cflocation
happens. Say for example you have page1, page2, and page3. Page1 is a
form, page2 processes the form, and page3 is a thank you page.
Server side (cflocation):
- user submits page1
- server processes page2
- server requests page3
- server processes page3
- server returns page3
Client side (using JS or HTML):
- user submits page1
- server processes page 2
- server returns page2
- browser requests page3
- server processes page3
- server returns page3
Maybe I'm wrong, but I don't think so...
+-----------------------------------------------+
Bryan Love
Macromedia Certified Professional
Internet Application Developer
Database Analyst
TeleCommunication Systems
[EMAIL PROTECTED]
+-----------------------------------------------+
"...'If there must be trouble, let it be in my day, that my child may have
peace'..."
- Thomas Paine, The American Crisis
-----Original Message-----
From: Jochem van Dieten [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 09, 2002 12:25 PM
To: CF-Talk
Subject: Re: cflocation vs. server side redirect.
Bryan Love wrote:
> server side redirects allow the use of cookies since the page is processed
> by the browser. Cflocations are faster since the relocation happens at
the
> server and does not have to go to the browser and back again (which is why
> cookies don't work with cflocation by the way).
This is incorrect. cflocation simply sends a HTTP 302 "Found" statuscode
to the browser together with a Location header. How could the URL one
sees in the browser possibly change if nothing was send to the browser?
> There are many different ways to do a client side redirect:
> - use <meta refresh=""> tag
> - use javascript window.location=""
> - use <body onload="window.location=''"
All of these depend on a user client understanding at least HTTP and
HTML (and possibly javascript). I would go for cflocation because that
only requires the user client to understand HTTP.
Jochem
______________________________________________________________________
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
