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 ______________________________________________________________________ This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
