> > 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?
And just to add one thing to Jochem's very accurate statement, you can use cookies with CFLOCATION in CF MX, and the reason you couldn't before was simply that the CF interpreter wouldn't let you. There's nothing wrong with using both a Set-Cookie and Location header in the same HTTP response. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ______________________________________________________________________ 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 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
