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

':authority' pseudo-header field support #9

Merged
merged 1 commit into from Aug 13, 2016
Merged

':authority' pseudo-header field support #9

merged 1 commit into from Aug 13, 2016

Conversation

syusui-s
Copy link
Contributor

@syusui-s syusui-s commented Jul 7, 2016

According to RFC7540 8.1.2.3, the client SHOULD use ':authority' request pseudo-header field instead of 'host' request header field.
There are some websites which does not respond to the request that contains 'host' header field.
If the request contains 'host', Google will close the connection immediately and the response by Twitter will be 404.

@ostinelli
Copy link
Owner

Thank you for your contribution. Can you please squash into a single reviewable commit, such a minor change should not require more. Thank you.

According to [RFC7540 8.1.2.3](https://tools.ietf.org/html/rfc7540#section-8.1.2),
the client SHOULD use ':authority' request pseudo-header field instead of 'host' request header field.
The format of authority is defined in [RFC3986, Section 3.2](https://tools.ietf.org/html/rfc3986#section-3.2).
'userinfo' is deprecated, and SHOULD NOT be included in the request headers.
@syusui-s
Copy link
Contributor Author

syusui-s commented Jul 7, 2016

Thanks for your reply. I squashed several commit into a single commit.

@ostinelli
Copy link
Owner

Thank you, will merge soon.

@ostinelli ostinelli merged commit 13e2b65 into ostinelli:master Aug 13, 2016
@ostinelli
Copy link
Owner

This is now merged in and released in 0.13.1. Thank you for your contribution!

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

Successfully merging this pull request may close these issues.

None yet

2 participants