<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't work. 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 Host with the leader in ColdFusion hosting. Voted #1 ColdFusion host by CF Developers. Offering shared and dedicated hosting options. www.cfxhosting.com/default.cfm?redirect=10481 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
