Pseudo Headers in Binary Representation of HTTP Messages (RFC 9292)

Hi all,

I have a question related to pseudo headers and binary http.

Here it says:

For field names, byte values that are not permitted in an HTTP field name cause the message to be invalid; see Section 5.1 of [HTTP] for a definition of what is valid and Section 4 regarding the handling of invalid messages. A recipient MUST treat a message that contains field values that would cause an HTTP/2 message to be malformed according to Section 8.2.1 of [HTTP/2] as invalid; see Section 4.

And later on:
Other pseudo-fields that are defined by protocol extensions MAY be included; pseudo-fields cannot be included in trailers (see Section 8.1 of [HTTP/2]). A Field Line containing pseudo-fields MUST precede other Field Line values. A message that contains a pseudo-field after any other field is invalid; see Section 4.

This is a bit confusing to me as if I follow the first paragraph it seems like it wouldnt be allowed to use β€œANY” pseudo-headers as β€œ:” is not a valid char in header names for HTTP. 


Received on Thursday, 6 July 2023 15:00:03 UTC