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
If the server sends multiple Set-Cookie headers, both the default and the requests client conflate those into one header-line, comma-separating the values -- which cookiejar cannot parse. Luckily, the urllib3 client keeps the headers as-is, so that it works in this case.
The text was updated successfully, but these errors were encountered:
Hrm, it's a mix-up between wsgiproxy and webtest, I think. For which actually requests is the perfect example, as they behave really sneaky regarding cookies: for their own cookie-handling they send off the urllib3 Response object (which has individual set-cookie headers) to the cookiejar, before wrapping it in their own requests Response object (which then conflates them) -- which doesn't work for webtest, since that operates on the completed Response object of the client: https://github.com/Pylons/webtest/blob/master/webtest/app.py#L659
If the server sends multiple
Set-Cookie
headers, both thedefault
and therequests
client conflate those into one header-line, comma-separating the values -- whichcookiejar
cannot parse. Luckily, theurllib3
client keeps the headers as-is, so that it works in this case.The text was updated successfully, but these errors were encountered: