Repository navigation
Section 5.4 (Host) in Semantics has normative 1.1 requirements #182
Description
In section 5.4, there are a couple of normative requirements for HTTP/1.1 ("A client MUST send a Host header field in all HTTP/1.1 request messages."; "A client MUST send a Host header field in an HTTP/1.1 request"; "A server MUST respond with a 400 (Bad Request) status code to any HTTP/1.1 request"), and it makes two references to the absolute-form production, which is defined in the Messaging draft (and hence is a dangling reference in Semantics). Those should probably live in Messaging, and the Semantics document should be more general.
Activity
reschke commentedon Feb 25, 2019
The references are dangling because the definition of "Host" moved (was in RFC 7230 before).
mnot commentedon Jul 2, 2020
E.g.,
and
mnot commentedon Jul 20, 2020
Looking for a place in messaging to move these. What about 3.3 Reconstructing the Target URI?
mnot commentedon Jul 29, 2020
@royfielding @reschke see question above ^^
reschke commentedon Jul 29, 2020
yes, 3.3 looks ok for that
mnot commentedon Aug 3, 2020
The end of 3.2 seemed like a better fit in the end; PTAL.
change log (#182)