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 QuizPlease log in to access this content. You will be redirected to the login page shortly.
LoginGeneral Tech Bugs & Fixes 2 years ago
Posted on 16 Aug 2022, this text provides information on Bugs & Fixes related to General Tech. Please note that while accuracy is prioritized, the data presented might not be entirely correct or up-to-date. This information is offered for general knowledge and informational purposes only, and should not be considered as a substitute for 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.
Please log in to access this content. You will be redirected to the login page shortly.
LoginReady to take your education and career to the next level? Register today and join our growing community of learners and professionals.
manpreet
Best Answer
2 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.