Incorrect. The client is sent a 302 status code - page moved.
> <CFLOCATION> is a redirect from the server side. Nothing on the > client takes > place. That's why setting cookies on pages that have CFLOCATION > doesn'twork This doesn't work because there's a bug in CF that was finally fixed in MX (it only took, oh, 6 years). It gets processed by the server and the server sends > a new page to the > browser. > > J > > -----Original Message----- > From: David K [mailto:[EMAIL PROTECTED] > Sent: Monday, June 02, 2003 11:07 AM > To: CF-Talk > Subject: CFLOCATION mechanism..? > > > Hoping someone can shed some light on the underlying mechanism that > CFLOCATION uses to perform the re-direct. My current understanding > is that > it simply returns a header to the browser for a client side re-direct. > However, I was testing to see if setting IE's "Allow META Refresh" to > "DISABLE" would break CFLOCATION and I was surprised to see that > it *did > not*. It did however break <cfheader name="refresh" value="0; > URL=foo.cfm">which makes sense. What's going on here? > > --David K. > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
