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
{{ message }}
Repository navigation
Cookies not saved after redirect (v5.0.0.pre3) #631
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 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...
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.
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.
Activity
tarcieri commentedon Dec 14, 2020
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 commentedon 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 commentedon Dec 14, 2020
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 commentedon 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 commentedon Jan 26, 2021
Hi @ixti @tarcieri is there a timeplan for releasing the new version? :)
tarcieri commentedon Jan 26, 2021
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.