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
Changing from option 1 to another option is an incompatible change, but it’s not likely to be a problem in practice.
Applications are not blocked by this issue. An application can implement whatever logic it wants by constructing a cookie header before the call to dial.
There is a similar situation with subprotocols. It is an error to specify subprotocols in the dialer and the header.
Let’s wait for new maintainer to make call on the right approach. Applications are not blocked by current code.
Description
If you manually pass
Cookie
header inDialContext(..., http.Header)
, cookies fromDialer.Jar
will be overwritten.Steps to Reproduce
Possible reason
From the first look I would say that this is happening because the part of code which is responsible for setting up all the passed headers ignores already applied
Cookie
header fromhttp.CookieJar
.The text was updated successfully, but these errors were encountered: