Re: [quicwg/base-drafts] http-core and Friends (#3513)

[Mike Bishop <[e-mail]>]

@MikeBishop commented on this pull request.



>  pseudo-header fields other than those defined in this document, except as
 negotiated via an extension; see {{extensions}}.
 
-Pseudo-header fields are only valid in the context in which they are defined.
-Pseudo-header fields defined for requests MUST NOT appear in responses;
-pseudo-header fields defined for responses MUST NOT appear in requests.
-Pseudo-header fields MUST NOT appear in trailers.  Endpoints MUST treat a
-request or response that contains undefined or invalid pseudo-header fields as
-malformed ({{malformed}}).
+Pseudo-fields are only valid in the context in which they are defined.

That's what it was in an earlier version of this PR; the pushback was that these only occur in the header, not in trailers, so it's more precise to say header fields than simply fields.  I agree that "pseudo-header field" makes it sound like there's a region called the "pseudo-header," and there kind of is since these have to be first, but we don't call it that.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/3513#discussion_r399463847