[Zope3-dev] Duplicate HTTP header handling

[Stuart Bishop]

Stuart Bishop wrote:
> Hi.
> 
> Currently if Z3 parses multiple headers with the same key, only the last is
> used.
> 
>>From reading section 4.2 of http://www.faqs.org/rfcs/rfc2616.html , I
> suspect the best way of handling this situation is to concatenate the
> duplicate headers into a comma seperated string.
> 
> I've noticed this when running Z3 behind cascading proxies and found I was
> losing X-Forwarded-For headers.
> 
> Does this seem like reasonable behavior? Some people may actually be relying
> on this (broken) behavior, but I have a need of accessing all the headers
> and don't want to have to use yet another tier to concatenate the headers as
> allowed by the RFC ;)

Looks like this has bitten people under Z2 as well:

http://www.zope.org/Collectors/Zope/908



-- 
Stuart Bishop <stuart at stuartbishop.net>
http://www.stuartbishop.net/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: OpenPGP digital signature
Url : http://mail.zope.org/pipermail/zope3-dev/attachments/20050812/d7a83b5b/signature.bin