Cookie differences #2253
Unanswered
EdLeafe
asked this question in
Potential Issue
Replies: 3 comments 3 replies
-
|
Anyone?? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Wow, over 2 months with no reply. Sad. |
Beta Was this translation helpful? Give feedback.
3 replies
-
|
So please feel free to close this issue. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have a project that used
requestswhen it was started, and then later was moved to async andaiohttp. Now I'm trying to replaceaiohttpwithhttpx, but I'm getting a failure that seems to be tied to howhttpxhandles cookies.The project is a tool for handling Mailman admin issues; it passes authentication and gets a list of outstanding issues as well as a cookie, which needs to be sent in the response for handling the outstanding issues. With
requestsandaiohttp, parsing the cookie values returns:But with
httpx, I see this:When I return that cookie to the server, the update request is rejected as unauthenticated, which doesn't happen with either
requestsoraiohttp.I've been replacing all my earlier async code that used
aiohttpwithhttpx, because I strongly preferhttpx. But this is a blocker for this project. The code flow is:What can be done differently in the handling of the cookies?
Beta Was this translation helpful? Give feedback.
All reactions