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

Host requirements in semantics #332

Closed
mnot opened this issue Mar 19, 2020 · 1 comment
Closed

Host requirements in semantics #332

mnot opened this issue Mar 19, 2020 · 1 comment

Comments

@mnot
Copy link
Member

mnot commented Mar 19, 2020

A client &MUST; send a Host header field in all HTTP/1.1 request messages.
If the target URI includes an authority component, then a client &MUST;
send a field value for Host that is identical to that authority
component, excluding any userinfo subcomponent and its "@" delimiter
().
If the authority component is missing or undefined for the target URI,
then a client &MUST; send a Host header field with an empty field value.

These are all H1 specific; only the first one is explicitly called out as so. I think this entire block should be moved to messaging, possibly in a new section?

@mnot mnot added the semantics label Mar 19, 2020
@mnot
Copy link
Member Author

mnot commented Mar 19, 2020

Dup of #182

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

No branches or pull requests

1 participant