Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.    By clickin

Search code, repositories, users, issues, pull requests...

submited by
Style Pass
2024-04-26 03:00:07

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

I have noticed an upwards trend in the number of websites that are broken for me due to service workers being published on them and then left to rot in my browser's caches. A while ago I ran a query on the status codes returned by over 400 service workers registered in my Edge browser and got the following HTTP response codes:

51 out of 416 service workers registered in my browser are registered on locations that now return 4xx response codes indicating the client made an error making the request. The failure mode from leaving a stale service worker on a site ranges from giving stale data to the website being completely inaccessible.

If you compare this to what the live site actually looks like you may notice it is very different. The ticket ordering does not work, and pretty much every page you can navigate to is not functional.

Leave a Comment