Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796)

guohuideng2024 left a comment (whatwg/fetch#1796)

In the http spec I found the syntax restriction of the "content coding", which gives us a complete list of possibilities.
(see the end of this comment for more details)

 `@unknown` looks good to me but I would like to confirm we don't want to use `?unknown` nor `[unknown]` instead? @annevk 

Hopefully nobody objects and I will update this PR with `@unknown` this Wednesday.

Cheers,
Guohui

+++++++++ details from http spec +++++++++++++++++++++++++++
http spec actually defines the syntax restriction of "content-coding" parameter.
Link to the http spec: https://www.rfc-editor.org/rfc/rfc2616
The "content-coding" is a "token", and the "token" is defined as the following:

   token          = 1*<any CHAR except CTLs or separators>
   separators     = "(" | ")" | "<" | ">" | "@"
                  | "," | ";" | ":" | "\" | <">
                  | "/" | "[" | "]" | "?" | "="
                  | "{" | "}" | SP | HT
// where:
CTL = <any US-ASCII control character
(octets 0 - 31) and DEL (127)>
SP = <US-ASCII SP, space (32)>
HT = <US-ASCII HT, horizontal-tab (9)>

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

Message ID: <whatwg/fetch/pull/1796/c2891520803@github.com>