You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yes, per HTTP spec you can have multiple headers with the same name. The semantics of how such values are processed are up to the particular header. In case of Set-Cookie all values are processed.
Okay, great. I did end up looking through the code and it seem straight forward. I wasn't sure if it used a hash or an array of [key, value] pairs, but it's the latter.
When proxying, say, HTTP/1.1, it's possible to receive a response with multiple
set-cookie
headers. How does this work in HTTP/2 and in this gem?Do we need to do something to handle this?
The text was updated successfully, but these errors were encountered: