- From: Patrick Meenan <notifications@github.com>
- Date: Mon, 16 Oct 2023 07:35:20 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 16 October 2023 14:35:27 UTC
`Sec-` makes sense if the header is meant to be forbidden. I can't speak directly to the extensible priorities spec since I was mostly an observer while the process went through but the end-to-end header intentionally allows for overrides by the origin and it's not immediately clear that the intent wasn't also to allow for the value to be application-specified or at least overridden. That said, it wouldn't hurt for both groups to align on when `Sec-` should be used and when it shouldn't. It also [came up](https://lists.w3.org/Archives/Public/ietf-http-wg/2023JulSep/0102.html) during discussions on compression dictionaries. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/issues/1718#issuecomment-1764617942 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/fetch/issues/1718/1764617942@github.com>
Received on Monday, 16 October 2023 14:35:27 UTC