Service worker navigation preload can use Search Prefetch requests
The service worker navigation preload is issued as part of a Service Worker navigation URLLoader interceptor. In a similar vein, Search Prefetch uses the same type of interceptor, but at lower priority. Once Service Worker has decided to intercept the navigation (generally, this means there is a fetch handler), it issues a direct network service request to get the resource when navigation preload is enabled in the service worker. This means lower priority interceptors are never consulted (i.e., app cache is not consulted, which is good; search prefetch is not consulted, which is not ideal). This CL adds functionality to handle synchronous interception decisions, but stops short of copying the interception logic in the navigation pathway that handles asynchronous decisions with multiple interceptors. Bug: 1155330 Change-Id: Iae225c0b4926946a4ec9fccc5dc5d240dc53c058 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2570392 Commit-Queue: Ryan Sturm <ryansturm@chromium.org> Reviewed-by:Matt Falkenhagen <falken@chromium.org> Reviewed-by:
Makoto Shimazu <shimazu@chromium.org> Cr-Commit-Position: refs/heads/master@{#835364}
Showing
Please register or sign in to comment