In this article, Scott Jehl suggests managing performance differently for new and returning visitors and that we could use a service worker (rather than a cookie) as a means of having the browser tell the server which category the request falls under.
The Clear-Site-Data HTTP header clears browsing data (cookies, storage, cache) associated with the requesting website. It can even be used to deregister service workers.
As a side note, I wonder if it might be an idea for me to update my website boilerplate to contain pages such as /clear-cookies, /clear-storage, and /clear-all. Then, if someone is having some weird cacheing-related problem on a website I developed, I can simply provide them with a link to one of those pages rather than asking them to hard-refresh or launch incognito windows.
Jeremy Keith suggests that it might be better if our websites ask people to grant permission for new content (e.g. blog posts or podcasts) to be silently cached, rather than asking permission to send intrusive notifications.
I’ve just implemented web push notifications on the Greenhill Journal so this is definitely food for thought.
See all tags.