Service Worker gets cached

[cloudlena]

What version of Cloud Foundry and CF CLI are you using? (i.e. What is the output of running cf curl /v2/info && cf version?

CLI 6.34.1 and CF 2.100.0

What version of the buildpack you are using?

1.4.22

If you were attempting to accomplish a task, what was it you were attempting to do?

Push an app created with create-react-app.

What did you expect to happen?

I expect the deployed service worker to be refreshed when I push a new version of the app.

What was the actual behavior?

The service worker gets cached for a very long time which causes my app to remain stale, even if I push new versions. I'm guessing that this is the same for anybody who uses service workers.

I'm guessing that we would need to add something like

location ~* ((serviceworker|service-worker)\.js)$ {
  add_header 'Cache-Control' 'no-store, no-cache, must-revalidate, proxy-revalidate, max-age=0';
  expires off;
  proxy_no_cache 1;
}

to the nginx config template.

The problem is described here.

The solution to this problem cor create-react-app for different hosting providers is described here but I'm unsure how I would apply this to Cloud Foundry since providing one's own nginx.conf is deprecated.

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/155135355

The labels on this github issue will be updated when the story is started.

[sclevine]

I suggest one of the following options:

1. Use the experimental NGINX buildpack: https://github.com/cloudfoundry/nginx-buildpack
2. Use the location_include directive in the Staticfile.

The staticfile buildpack is intended to be used to host static content, not web applications.

(@dgodd)

[cloudlena]

Thanks, @sclevine. Using location_include is a good idea. I'll give it a try. However, I still think it would still be a good thing to provide a way for users to disable caching for certain locations.

[patrickliangli]

@mastertinner , did you find a solution to this problem? I am also having the same issue.

[cloudlena]

@patrickliangli, I haven't tried anything specific yet. As far as I can tell, putting my code snippet from above into a location_include should work though.

[astrieanna]

This seems to have been resolved by either of the two options @sclevine gave.