-
Notifications
You must be signed in to change notification settings - Fork 427
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
Incorrect Host header used on redirected requests #693
Labels
Comments
mmm are you sure of this? The rfc says
Was the port different from 80 or 443? I will write a test for it anyway. |
Yes, that's what I meant by "non-standard port." |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When a request is made to a server running on a non-standard port, the port should be included in the Host header. This is part of RFC-2616.
When
follow_redirect
is enabled and the client gets a 302 redirect, hackney's request to the new target includes a Host header for the new host but it does not include the port. When used with strict servers, this results in a bad request response.The text was updated successfully, but these errors were encountered: