Define the header value parser

[annevk]

Although #6 is closed, #6 (comment) still seems relevant:

Another consideration that comes up routinely when dealing with HTTP fields is the potential for them to be repeated, which can happen by accident more often than expected. Under those conditions, it is possible that the values are combined.

In this case, that could produce results like Sec-GPC: 1, 1 at a receiving entity. A simple parser that does simple comparisons (headers.get("sec-gpc") == "1") will make a mistake.

(Although TBD if that's a mistake or not I suppose.)

[pes10k]

Hi @annevk , apologies for letting this sit for so long.

TBH I don't know how to answer your question. I understand the technical question / issue but, I'm not sure the correct standards-way to answer.

Is there an existing enum-like list of "HTTP header parsing modes" already defined, and we just need to state which one to use for GPC? If this is the case, could you point me to that list? That'd be very appreciated.

Otherwise, are there any specs that come to mind that do a good, clear job of defining header value parsing we could model off?

[annevk]

Fetch, in particular Content-Length and Content-Type are good precedent in terms of how to specify a header parser.

[mnot]

Another example is the structured fields spec...