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

• From: Norman Maurer <norman_maurer@apple.com>
• Date: Wed, 05 Jul 2023 19:49:51 +0200
• To: ietf-http-wg@w3.org
• Message-id: <97575C96-6EF5-48C7-9788-23C18D4E973A@apple.com>

Hi all,

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

https://www.rfc-editor.org/rfc/rfc9292.html#section-3.6

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. 


Thanks,
Norman

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