Re: Working Group Last Call: HTTP/2 revision

Am 30.08.2021 um 01:22 schrieb Martin Thomson:
> On Sat, Aug 28, 2021, at 02:37, Julian Reschke wrote:
>> PS: I'll be happy to create PRs if desired.
>
> I'd appreciate that, thanks.
>
> (most of these are changes in old text, but I see no reason not to make improvements where possible)

Done that.

Below a few more nits about Section 8:

8.1.1

A malformed request or response is one that is an otherwise valid
sequence of HTTP/2 frames but is invalid due to the presence of
extraneous frames, prohibited fields or pseudo-header fields, the
absence of mandatory fields or pseudo-header fields, the inclusion of
uppercase field names, or invalid field names and/or values (in certain
circumstances; see Section 8.2).

Q: are there any mandatory fields that are not pseudo-header fields?


8.2

To improve efficiency and interoperability, field names MUST be
converted to lowercase when constructing an HTTP/2 message.

Q: I think this is somewhat misleading, it just provides the motivation
why the lowercase format was introduced initially. I would just remove
the sentence and potentially insert a note about lower-casing into the
field name validity statements.


8.3

The prose keeps re-referencing 8.1.1; doing so once (while just
hyperlinking the term "malformed") would be sufficient (I believe this
style of over-referencing is present in other parts of the spece as well).


Best regards, Julian

Received on Tuesday, 31 August 2021 14:56:24 UTC