- From: Daniel Abrecht <notifications@github.com>
- Date: Sun, 20 Aug 2023 05:47:15 -0700
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Sunday, 20 August 2023 12:47:22 UTC
That's not what I'm proposing. I'm proposing that, when an origin installs it's worker, a `Service-Worker-Exclude` header can be provided to exclude certain locations on it's own origin from being handled by it. My understanding is, that it already doesn't matter where a request came from, but only where it goes to, for which service worker is going to handle it, and that the `Service-Worker-Allowed` header already operates in a similar way regarding when it needs to be set. My proposal doesn't change any of that. It just allows to make sure some locations won't be handled by a service worker. I do have a use-case where this would be useful, by allowing me to make sure the client side of my application won't be able to intercept a request to a specific location on my applications origin. But that is just a use-case, something this would be useful for, not the proposal itself. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/ServiceWorker/issues/1690#issuecomment-1685276603 You are receiving this because you are subscribed to this thread. Message ID: <w3c/ServiceWorker/issues/1690/1685276603@github.com>
Received on Sunday, 20 August 2023 12:47:22 UTC