- From: Domenic Denicola <notifications@github.com>
- Date: Thu, 28 Apr 2022 12:05:53 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 28 April 2022 19:06:06 UTC
> I can go with an option where if the destination of the request is `script` it can process any link header, and if it's `style` it can process any `as=font`/`as=img`/`as=style` link header, allowing all the link semantics. It's not more layer-violating than CSP as it only deals with request destinations. OK, so concretely, Fetch would contain this logic, which dispatches to HTML's "process link headers for subresources" which just assumes that if it's called it's allowed to do full `Link` processing. (Maybe it doesn't even need to be subresource-specific.) That sounds pretty elegant to me. @annevk are you on board? -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/pull/1409#issuecomment-1112559804 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/fetch/pull/1409/c1112559804@github.com>
Received on Thursday, 28 April 2022 19:06:06 UTC