Allow repeated HTTP Headers defined in the Response
Apiary only supports one occurrence of each Response Header. If multiple headers are included in the API Blueprint, only the last one is represented in the documentation.
This is problematic when documenting that an API Response sets multiple cookies.
Per RFC 6265: " 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."
Suggestion: Modify the behavior to support multiple occurrences of headers, or at least of the "Set-Cookie" header.
Nicolas Joseph commented
Hi! did that regress?
I got a spec with 2 `Set-Cookie` header that result in just the first one being set.
AdminLukas Linhart (Admin, apiary.io) commented
could you please provide the snippet blueprint and what functionality doesn't work for you?
On parser level, multiple Set-Cookies should be supported: https://github.com/apiaryio/snowcrash/issues/75#issuecomment-58886108
We intent to support it in our ecosystem as well and we are interested in eventual gaps.