Hi
In the bad-old days I did my cgi programming in C++, and I wrote out the
headers by hand. Back then, browsers (NS2, for example) did not handle the
case when both Set-cookie and Location headers were included in a response.
That may have lead to earlier versions of CF not needing to "do the right
thing", because it didn't work anyway.
On the up side, my web site no longer supports NS2, so I'm pleased to see
the new support in CFMX!
Mark
-----Original Message-----
From: Dave Watts [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 12, 2002 5:52 PM
To: CF-Talk
Subject: RE: cookie/location
> I never thought of this as an 'issue'. I thought it
> was just the nature of the client-server relationship.
> If the page never makes it to the client (as it was
> my understanding that <cflocation> executes 100% server
> side), then the cookie couldn't/wouldn't be set.
This isn't really the case. When you use CFLOCATION in a page, the server
returns an HTTP response to the browser. This response contains a Location
header, which instructs the browser to request another URL. There's no
reason why the response can't also contain a Set-Cookie header, but CF in
the past wouldn't let you do both at the same time. Other CGI programming
languages/environments did allow this.
Of course, you could have worked around this limitation in previous versions
by simply using CFHEADER to "manually" set the Location and Set-Cookie
headers in the same page request, I suppose.
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/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
