Embark on a journey of knowledge! Take the quiz and earn valuable credits.
Take A QuizChallenge yourself and boost your learning! Start the quiz now to earn credits.
Take A QuizUnlock your potential! Begin the quiz, answer questions, and accumulate credits along the way.
Take A QuizKindly log in to use this feature. We’ll take you to the login page automatically.
LoginGeneral Tech Bugs & Fixes 3 years ago
User submissions are the sole responsibility of contributors, with TuteeHUB disclaiming liability for accuracy, copyrights, or consequences of use; content is for informational purposes only and not professional advice.
It was on the IIS server side, what I did was set a max-age to 60 header, and also disabled the CACHE on this particular site. This meant that the service-worker took over cache control, and I could see it updating as I change version number. So in other words IIS was caching the service-worker file
No matter what stage you're at in your education or career, TuteeHUB will help you reach the next level that you're aiming for. Simply,Choose a subject/topic and get started in self-paced practice sessions to improve your knowledge and scores.
Kindly log in to use this feature. We’ll take you to the login page automatically.
LoginReady to take your education and career to the next level? Register today and join our growing community of learners and professionals.
Your experience on this site will be improved by allowing cookies. Read Cookie Policy
Your experience on this site will be improved by allowing cookies. Read Cookie Policy
manpreet
Best Answer
3 years ago
Recently created a PWA with service-worker and everything runs great on local testing server, the resources and cache gets updated on each version change of the service-worker.
I am getting a problem though with a live IIS Win server, where it seems its serving server cache above the service-worker cache, or perhaps a cached version of the service-worker. Has anyone ran into this problem with an IIS Win Server? The PWA is html and js based.