Amodio
commented
9 months ago It works as expected in Python:
$ cat test.py
import requests
response = requests.get("http://dubbelboer.com/302cookie.php")
if response.status_code == 200:
print(response.text)
else:
print(f"Error: {response.status_code}")
final_url = response.url
print(f"Final URL: {final_url}")
$ python3 test.py
Cookie was: SET<br><a href="?a=1701349447.3061">try again</a>
Final URL: https://dubbelboer.com/302cookie.php?show=1701349447.2922
bcmills
seankhliao
Go version
go version go1.19.8 linux/amd64
What operating system and processor architecture are you using (
go env)?What did you do?
First case, I did a GET onto a webpage that sets a cookie and redirects users: https://go.dev/play/p/ecskkzjvHRy Second case, I did a POST onto a webpage that sets a cookie and redirects users: https://go.dev/play/p/a4xWVv0ZVqT
What did you expect to see?
In both cases, I expected a redirection to a webpage with cookies set. It turns out that a Cookie Jar has to be defined/initialized for this behaviour to happen (see here for example). Corrected code for each case: GET & POST. Output in the first case:
In the second case, I got a Wrong Credentials error.
What did you see instead?
First case:
Second case detailed log (censored):
As pointed out in this 2012 blog post, most browsers redirect users by setting cookies and Golang does only half of this job by default. Please make this default, or do not redirect by default.