Re: multiple Set-Cookies (was Re: require-client functionality)

["Roy T. Fielding" <fi...@avron.ICS.UCI.EDU>]

> Neither Netscape nor MSIE understand multiple cookies on one Set-Cookie
> header.  So you need to send three headers.  I wish I could find the
> time to do this right -- because I need it in the hotwired server.  If
> you want to see a cookie mess, go visit our site.  We spam you with a p
> cookie on each request (to detect "bad" proxies).
> ...
> 
> Ya know, adhering to 1.1 is fine and all... but there's a lot of existing
> practice it might be worth considering.

Why should I define HTTP as "existing practice" just because existing
developers appear to be incapable of reading a specification?  Folding
of header fields has been around much longer than cookies, and is
performed by the message parser BEFORE it knows what any of the field
names mean.  Even if we kludged Apache for the workaround, it still
wouldn't work through proxies.  The only real solution is to not use
multiple Set-Cookies until they fix their bloody parser.

......Roy