-
Notifications
You must be signed in to change notification settings - Fork 322
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cookies not saved after redirect (v5.0.0.pre3) #631
Comments
@tarcieri thank you for the info and sorry for the dup. No I can decide, if I want to have the request stored in the response, or having a working cookie handling. Do you plan to create a new stable version? |
We should definitely do another release soon, unfortunately we recently had a regression in the test suite (#627) which should get fixed before we do that. |
Sorry was super off lately. Getting back to development slowly, so stay tuned and good things will be happening soon... :D |
We should probably open a 5.0.0 release tracking issue / milestone. In the meantime we should probably do another prerelease. There are some showstopper issues (#627) preventing another release, and notably issues surrounding the parser (#604, #622, #630, #639) which it would be great to have addressed before a final release. |
I'm using the version v5.0.0.pre3 cause I need the request information in the response.
There is a problem in an api which uses redirects. After the 301redirect, the request does not contain the cookie information.
My Workaround is to make a Request without following the redirect, save the cookie and do it again with the cookie, but in my mind this should work automatically.
The text was updated successfully, but these errors were encountered: