Skip to content
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

Closed
c2ofh opened this issue Dec 14, 2020 · 6 comments
Closed

Cookies not saved after redirect (v5.0.0.pre3) #631

c2ofh opened this issue Dec 14, 2020 · 6 comments

Comments

@c2ofh
Copy link

c2ofh commented Dec 14, 2020

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.

@tarcieri
Copy link
Member

Dup of #264.

Support for this landed in #613. In order to use it for now, you'll need to use the gem via git as #613 has not made it into any release yet.

@c2ofh
Copy link
Author

c2ofh commented Dec 14, 2020

@tarcieri thank you for the info and sorry for the dup.
I thought v5.0.0.pre3 is the newest version.

No I can decide, if I want to have the request stored in the response, or having a working cookie handling.
I need both, so I might not be able to switch the project from HTTParty to this nice gem...

Do you plan to create a new stable version?

@tarcieri
Copy link
Member

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.

@ixti
Copy link
Member

ixti commented Dec 15, 2020

Sorry was super off lately. Getting back to development slowly, so stay tuned and good things will be happening soon... :D

@c2ofh
Copy link
Author

c2ofh commented Jan 26, 2021

Hi @ixti @tarcieri is there a timeplan for releasing the new version? :)

@tarcieri
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants