> Does it use the META REFRESH then or ? The only reason I ask is that you > cannot set cookies on a template with CFLOCATION, but I am pretty sure > you can when META REFRESH is used?
No its quite different to a meta refresh. It takes place in the HTTP headers not the <head> section of the HTML. With HTTP you have a bunch of status codes that the server & client use to talk to each other: 1xx - Informational 2xx - Successful 3xx - Redirect 4xx - Client error (eg. 404 "not found" or 403 "forbidden") 5xx - Server error - http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html I think CF uses a 303 or 307 for its cflocation. This is essentially the same as: <!--- there may be some other header information before this ---> <cfheader statusCode = "303" statusText = "Location:http://someotherurl.com";> (To make sure get your hands on mozilla and the livehttpheaders plugin - an excellent tool for watching what is happening at the http level.) The client (browser) reads this information back from the server and sends a new request for the http://someotherurl.com url. The end user probably won't see much apart from the url suddenly changing in their address bar. These HTTP based redirects are a much nicer way of moving clients around than <meta> or javascript based redirects. So instead of putting up a "This page has moved - please update your bookmarks then click here or wait to be redirected" message use an HTTP 301 - moved permanently and let the client's software deal with the updates to bookmarks and redirection. As for the cookie stuff - didn't know about that. Cheers Mark ______________ Mark Stanton Web Production Gruden Pty Ltd Tel: 9956 6388 Mob: 0410 458 201 Fax: 9956 8433 http://www.gruden.com --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MX Downunder AsiaPac DevCon - http://mxdu.com/
