I'm hosting a PHP 8, laravel 8.x, application on Azure via an App Service. Inside of my NGINX configuration, I specify the following:
add_header Cache-Control "no-cache, must-revalidate";
Now, this shows in the response headers but Azure appears to be overloading this with its own that looks to be taking presedence in the browser:
My NGINX configuration does not contain this "no-cache, private" header. Due to this being a SPA application, the javascript changes are causing people to need to re-validate via a cache-clear on each individual page.
Is there some way in Azure I can stop this and keep it as only "no-cache, must-revalidate"?
Update: I have since changed it to add_header Cache-Control "no-cache, no-store, must-revalidate"; but the no-cache, private seems to still be taking presedence.
