You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Basic Demo in the service worker samples page performs different actions on the requests depending on the location, stating in a comment: "// Skip cross-origin requests, like those for Google Analytics."
As far as I understand, Service Workers can't intercept cross-domain requests, so this might mislead others (as it did me) into thinking that this would be possible.
The text was updated successfully, but these errors were encountered:
It's definitely possible for a service worker's fetch event handler to respond to a cross-origin request.
A service worker can only control a same-origin web page that's under it's scope. If that web page makes a request for a cross-origin resource, via a fetch('https://cross-origin.example.com') or some other loading mechanism, like <script src="https://cross-origin.example.com">, the fetch event handler will be fired and the service worker can respond.
The Basic Demo in the service worker samples page performs different actions on the requests depending on the location, stating in a comment: "// Skip cross-origin requests, like those for Google Analytics."
As far as I understand, Service Workers can't intercept cross-domain requests, so this might mislead others (as it did me) into thinking that this would be possible.
The text was updated successfully, but these errors were encountered: