Additional information, screenshots, or code examples
note that the sid cookie appears twice in the set-cookie header: once at the beginning to clear it, once at the end to set it. i'm not sure if this is related.
i guess these are technically 2 set-cookie headers, but they're all joined with a ,, whereas curl, etc, show them as separate headers -- which is useful for debugging. is there a way to show these separately using httpie?
User agents MUST implement the more liberal processing rules defined in Section 5, in order to maximize interoperability with existing servers that do not conform to the well-behaved profile defined in Section 4.
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.
Checklist
Minimal reproduction code and steps
see httpie debug output below from WSL. also repro'd on Ubuntu 22.10
Current result
sid
cookie is not being setExpected result
sid
cookie should be set. it works correctly using Chrome, Firefox, curl, and Python/requests with or without asession
.Debug output
Please re-run the command with
--debug
, then copy the entire command & output and paste both below:I've redacted actual token and cookie values with
XXX123
.Additional information, screenshots, or code examples
note that the
sid
cookie appears twice in theset-cookie
header: once at the beginning to clear it, once at the end to set it. i'm not sure if this is related.i guess these are technically 2
set-cookie
headers, but they're all joined with a,
, whereas curl, etc, show them as separate headers -- which is useful for debugging. is there a way to show these separately using httpie?Edit:
https://www.rfc-editor.org/rfc/rfc6265