Re: [whatwg/fetch] Update RFC 7234 usage to RFC 9111 (Issue #1558)

Let's see:

* `field-name`: unchanged.
* `method`: unchanged.
* `field-content`: unchanged.
* `field-value`: changed, but we don't rely on this currently despite it being listed in the source so maybe it doesn't matter. Our restrictions on header values are much looser than HTTP. The note near "header value" needs to reference https://github.com/httpwg/http-core/issues/215 though. That's closed, but it's not clear to me the HTTP WG is willing to engage further on this topic.
* `reason-phrase`: unchanged, but no longer defined in semantics. I guess it's a pure HTTP/1.1 thing now.
* `delta-seconds`: unchanged.

I think most of the tricky issues with fields are avoided because we don't talk about trailers at the moment. If we ever got trailer support it might give rise to some confusion as we'd use header list and `Headers` for them. As header list and `Headers` is really our "fields". Still, we should add a note that we use the colloquial term.

Ah, and I just noticed there's a bunch of hardcoded links for HTTP caching as also noted above. Hopefully those are somewhat straightforward.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/1558#issuecomment-1373835296
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/issues/1558/1373835296@github.com>