- From: Mike West <notifications@github.com>
- Date: Tue, 05 Jun 2018 08:24:59 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 5 June 2018 15:25:22 UTC
Hey, @youennf! > Is it to allow a simpler definition/implementation of `Sec-Metadata`? Right now, `Sec-Metadata` defines a `target` attribute to describe the target browsing context of a navigation request: https://mikewest.github.io/sec-metadata/#target-member. It would be ideal if we could get rid of that member by folding the `top-level`/`nested` distinction into the `destination`. > Is it to allow service worker to start acting as some sort of security proxy that could decide to stop loads based on a better knowledge of the client triggering the fetch? That's also a distinction that I think might be useful, but it's not _my_ intent. Offering that capability to developers would be a happy side-effect of this change. :) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/issues/755#issuecomment-394752116
Received on Tuesday, 5 June 2018 15:25:22 UTC