This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author piotr.dobrogost
Recipients ajaksu2, barry, beazley, bmiller, eric.araujo, ezio.melotti, georg.brandl, jhylton, jjlee, joel.verhagen, orsenthil, petri.lehtinen, piotr.dobrogost, srid
Date 2013-01-08.22:02:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1357682530.61.0.509745759312.issue4773@psf.upfronthosting.co.za>
In-reply-to
Content
@joel.verhagen

"Should HTTPResponse.getheaders() comma-separate the values (...)"

No, it should not. RFC 2616 states:

"Multiple message-header fields with the same field-name MAY be present in a message if and only if the entire field-value for that header field is defined as a comma-separated list [i.e., #(values)]."

As field-values for some header fields ('Set-Cookie' being an example) are not defined as a comma-separated list such fields must not be merged.

Side note:
RFC 2616 is very soon to be obsoleted by the new RFC from httpbin working group. However, in the current/newest draft (http://trac.tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-21#section-3.2) although wording is different the sense is the same.
History
Date User Action Args
2013-01-08 22:02:10piotr.dobrogostsetrecipients: + piotr.dobrogost, jhylton, barry, georg.brandl, beazley, jjlee, orsenthil, ajaksu2, bmiller, ezio.melotti, eric.araujo, srid, petri.lehtinen, joel.verhagen
2013-01-08 22:02:10piotr.dobrogostsetmessageid: <1357682530.61.0.509745759312.issue4773@psf.upfronthosting.co.za>
2013-01-08 22:02:10piotr.dobrogostlinkissue4773 messages
2013-01-08 22:02:10piotr.dobrogostcreate