check-gatsby-caching
check-gatsby-caching copied to clipboard
It fails for page-data and js/css when site is deployed with pathPrefix
When deploying a Gatsby site with pathPrefix, like:
https://www.example.com/prefix/
the output of the tool is this:
Validating headers for the Gatsby site: https://www.example.com/prefix/
HTML
https://www.example.com/prefix/
✅ headers are correct!
app-data.json
https://www.example.com/prefix/page-data/app-data.json
✅ headers are correct!
Page Data
https://www.example.com/prefix/prefix/page-data\index\page-data.json
❌
- Expected
+ Received
Object {
- "max-age": 0,
- "must-revalidate": true,
- "public": true,
+ "null": "No cache-control header set",
}
JavaScript and CSS
https://www.example.com/prefix/prefix/webpack-runtime-4cd53e51decca410c49d.js
❌
- Expected
+ Received
Object {
- "immutable": true,
- "max-age": 31536000,
- "public": true,
+ "null": "No cache-control header set",
}
It seems to fail to call the correct files to check the headers for (the last two get 404, because the prefix is repeated and the url is wrong), while the gatsby site calls them correctly, so the pathPrefix is properly configured.