Skip to content

Commit

Permalink
docs(gatsby-plugin-offline): specify to not HTTP-cache sw.js (gatsbyj…
Browse files Browse the repository at this point in the history
  • Loading branch information
vtenfys authored and gpetrioli committed Jan 22, 2019
1 parent f2e1b29 commit f0e300d
Showing 1 changed file with 2 additions and 0 deletions.
2 changes: 2 additions & 0 deletions docs/docs/caching.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,8 @@ JavaScript and CSS files _generated by webpack_ should also be cached forever. L

The `cache-control` header should be `cache-control: public, max-age=31536000,immutable`

The only exception to this is the file `/sw.js`, which needs to be revalidated upon each load to check if a new version of the site is available. This file is generated by `gatsby-plugin-offline` and other service worker plugins, in order to serve content offline. Its `cache-control` header should be `cache-control: public, max-age=0, must-revalidate`

## Setting up caching on different hosts

How you setup your caching depends on how you host your site. We encourage people to create Gatsby plugins per host to automate the creation of caching headers.
Expand Down

0 comments on commit f0e300d

Please sign in to comment.