On a future visit to the site after the application code has changed:
The browser loads https://www.example.com/ which contains <script src="//static.example.com/app/main.js/125">.
The browser matches the /app/main.js/125 request with the /app/main.js path of the previous response that is in cache and requests https://static.example.com/app/main.js/123 with Accept-Encoding: br, gzip, sbr, sec-fetch-mode: cors and sec-bikeshed-available-dictionary: <SHA-256 HASH>.
The server for static.example.com matches the URL and hash with the pre-compressed artifact from the build and responds with it and Content-Encoding: sbr, Access-Control-Allow-Origin: https://www.example.com, Vary: Accept-Encoding,sec-bikeshed-available-dictionary.
I believe it should say:
The browser matches the /app/main.js/125 request with the /app/main.js path of the previous response that is in cache and requests https://static.example.com/app/main.js/125 with Accept-Encoding: br, gzip, sbr, sec-fetch-mode: cors and sec-bikeshed-available-dictionary: <SHA-256 HASH>.
pmeenan
commented
1 year ago
The README.md says:
On a future visit to the site after the application code has changed:
<script src="//static.example.com/app/main.js/125">./app/main.js/125request with the/app/main.jspath of the previous response that is in cache and requests https://static.example.com/app/main.js/123 withAccept-Encoding: br, gzip, sbr,sec-fetch-mode: corsandsec-bikeshed-available-dictionary: <SHA-256 HASH>.Content-Encoding: sbr,Access-Control-Allow-Origin: https://www.example.com,Vary: Accept-Encoding,sec-bikeshed-available-dictionary.I believe it should say:
The browser matches the
/app/main.js/125request with the/app/main.jspath of the previous response that is in cache and requests https://static.example.com/app/main.js/125 withAccept-Encoding: br, gzip, sbr,sec-fetch-mode: corsandsec-bikeshed-available-dictionary: <SHA-256 HASH>.