Some of each, in a way. cflocation sends a redirect header to the browser. Because it's a header, it has to come before content, and why it won't work after a cfflush. At this point, the server stops sending any data (stops processing the page, really) so no content ever reaches the browser. The browser then (if it's behaving properly) issues a new request, sans cookies, to the page specified in the redirect header.
--Ben Ben Nadel wrote: > Snake, Jon, > > While CFLocation IS coldfusion, it actually goes go across to the browser. I > believe it sends a meta redirect or something of that nature. So it IS cold > fusion, but it is NOT server side, as far as I understand. > > Because of this, CFLocation will not work if you have already flushed > content to the browser (via CFFlush or some other method) since at that > point it is too late for the server to update the headers with the redirect. > > So, if its just not working, try putting some cfsilent tags around the code > surrounding the CFLocation and make sure you are not writing to the browser > first. > > Sorry if there is some misinformation there, but I think that's the jist of > it. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:226501 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
