Service worker cache messing with authentication

Hello there ! Thanks for the amazing work !

I am trying to make OHIF work behind a reverse-proxy which handles authentication. When unauthenticated, it simply redirects to the login page.

The problem is, whenever the status changes (when logging-in or logging-out), the OHIF page is broken, because it caches everything : the browser’s request to / gets answered by the ServiceWorker, which prevents my reverse-proxy redirection.

Is there a way to disable the caching for the main page?

[arantes555]

@dannyrb thanks for your help, but I managed to work-around my problem by not putting OHIF itself, but only the backend it connects to, behind the authenticating reverse-proxy, then using the httpErrorHandler option of app-config.js to redirect to the login page upon 401.

I must however point out that having index.html cached this aggressively seems to me to be contrary to usual best-practices… For example, if the server updates its version of OHIF Viewer, a client can basically never get the new version without doing a manual Hard reload. From what I have seen most often in deployments, the main page (which is usually pretty light anyway in modern SPAs) is not cached at all, and calls resources (JS and CSS) with unique names (random, or even hashes), so they are cached as much as possible, but are updated as soon as the main page requests a new version.

[pieper]

Thanks, @dannyrb I’ll keep an eye open for when this happens so I can document how to reproduce and file a report. Basically I was just using the http-server package on a static site and it would not load unless I used command-shift-R.