Recently I’ve been researching how to use service workers to speed up traditional, multi-page websites rather than SPAs. Some Googlers have been promoting the use of streaming responses. A header chunk is cached client-side and returned immediately for every navigation, so the page can start constructing the CSSOM and do an initial render while it’s still waiting on page-specific content from the server. I’ll get into the why and how of that in a later post after I figure a few more things out.
Right now, I want to ask those in the know about a problem I’ve run into and see if they have a solution.
Pages render without styles when cacheing causes mismatches between CSS and markup. Which seems silly. Surely this is a solved problem?
On a normal website, we avoid this problem by adding some fingerprint to the end of the asset URLs to make sure that the page’s content gets the versions of styles and scripts that the content expects.
But the same isn’t true when the header chunk is cached locally but page content is streamed from the server. The cached header markup may include an out-of-date CSS url that is then applied to content from the server that expects newer styles.
Here’s the specific flow where this happens:
The result is one very ugly page. (I’m assuming your page looks worse without its styles, which I guess is not a guarantee on today’s web.) The same can easily happen with scripts, but with styles it’s much simpler to see.
What if we just ignore it? I don’t refactor my css fully that often, so it’s usually fine for one page view to show old styles. But in the fragile world of container microservice edge-cached web things, I already have enough unintended consequences to think through each launch. I don’t want to add manual CSS cache invalidation to the list. I’d like an automated solution that works correctly all the time.
Let me restate the problem: if our service worker is streaming the body of a page from the server, it needs to check if the styles in the local cache are up-to-date with the server. If not, it should abort the streaming response, load the full page from the server, and let an updated service worker take over.
In the most common case, we will soon be able to do better. If the first request that needs to hit the server is also the first page view in the session, browsers will soon do a navigation preload, requesting the full page immediately, while the service worker is still booting up and before it has a chance to handle the request from the cache. Normally we would throw out that preload request if the cache can answer faster, but not in this case. To avoid a css/markup mismatch, the service worker should instruct the browser to use the preload full page request and then unregister itself. The full page request will then have matching styles and markup and can register a new version of the service worker immediately.
(Above, I’m simplifying by only considering the case where the network is available and reasonably fast. Otherwise, the service worker should still use the cached header and whatever “not available” treatment it normally shows if streaming a page body times out.)
So: service worker and streams braintrust, is there a solution I’m missing? Or is this the best we can do for now?