Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support multiple Set-Cookie headers as described in RFC 6265 #12

Open
sebastian-philipp opened this issue Mar 21, 2016 · 0 comments
Open

Comments

@sebastian-philipp
Copy link

Hi,

from RFC-6265 3. Overview:

  1. Overview

[...] An origin server can include multiple
Set-Cookie header fields in a single response. [...]

Origin servers SHOULD NOT fold multiple Set-Cookie header fields into
a single header field. The usual mechanism for folding HTTP headers
fields (i.e., as defined in [RFC2616]) might change the semantics of
the Set-Cookie header field because the %x2C (",") character is used
by Set-Cookie in a way that conflicts with such folding.

It looks like the current THeaderHash implementation cannot cope with multiple Set-Cookie headers at the moment.

Sebastian

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants