InetHeaderMap doesn't support multiple headers with the same name

[japplegame]

This is actual for Set-Cookie header. It is impossible to parse client request cookies.

[s-ludwig]

I'll look into it.

[japplegame]

It is critical for me and I'm ready to write pull request immediately, but I don't know how to implement this without breaking existing code. I think headers should not be an associative array, but just a list.

[japplegame]

May be we need something like InetHeaderList?

[s-ludwig]

Wait a little. The current behavior is according to the old RFC822 standard, which is to append all equally named headers to a single comma separated list. So you can implement this right now by just splitting the "Cookie" field by ",".

However, since this is now obsolete behavior (multiple occurrences of the same field are not defined anymore in RFC 5322), it makes sense to make a transition to allow multiple fields with the name name in InetHeaderMap. However, this requires a bit of careful testing to make sure nothing breaks (I think nothing depends on the comma separation right now, though). I already have the support for multiple fields ready and will commit as soon as I can make reasonably sure that it will not impact anything else.

[japplegame]

So you can implement this right now by just splitting the "Cookie" field by ","

No. I can't. Because comma used in expires field. For example expires=Fri, 08-Nov-2013 15:22:33 GMT

[s-ludwig]

Damn, you are right. You could still parse it, but not as easy. Anyway, as said I have a full solution almost ready, so that shouldn't be necessary. Get a coffee and check back again ;)

[japplegame]

It works! Many thanks!