sbp commented on issue #41:
URL: https://github.com/apache/tooling-docs/issues/41#issuecomment-3118142130

   I [broke the hash 
deliberately](https://github.com/apache/tooling-docs/commit/b8e59f552a82f251aa3143b53cffab09e7585ef1),
 and now the browser tells me:
   
   > None of the “sha384” hashes in the integrity attribute match the content 
of the subresource at “https://tooling.apache.org/js/bootstrap.bundle.min.js”. 
The computed hash is 
“OERcA2EqjJCMA+/3y+gxIOqMEjwtxJY7qPCqsdltbNJuaOe923+mo//f6V8Qbsw3”. 
tooling.apache.org
   
   This means that the browser is reporting a *different* hash for 
https://tooling.apache.org/js/bootstrap.bundle.min.js compared to 
https://tooling-sbp-test.staged.apache.org/js/bootstrap.bundle.min.js but, 
again:
   
   ```
   $ curl -s https://tooling.apache.org/js/bootstrap.bundle.min.js | shasum -a 
384
   
4d8300fae031e1fe37ae29713c886696a03e562fb16f231ef98551dc170bd793721cba9dfbb59836dc813dd6b288e3f1
  -
   
   $ curl -s 
https://tooling-sbp-test.staged.apache.org/js/bootstrap.bundle.min.js | shasum 
-a 384
   
4d8300fae031e1fe37ae29713c886696a03e562fb16f231ef98551dc170bd793721cba9dfbb59836dc813dd6b288e3f1
  -
   ```
   
   So at this point I of course suspect caching, navigate to 
https://tooling.apache.org/js/bootstrap.bundle.min.js and reload it manually, 
and indeed the message changes:
   
   > None of the “sha384” hashes in the integrity attribute match the content 
of the subresource at “https://tooling.apache.org/js/bootstrap.bundle.min.js”. 
The computed hash is 
“TYMA+uAx4f43rilxPIhmlqA+Vi+xbyMe+YVR3BcL15NyHLqd+7WYNtyBPdayiOPx”. 
tooling.apache.org
   
   This is the same hash as given on tooling-sbp-test. What I expect happened 
is that the changes in #27 did indeed cause a mismatch with the `integrity` 
value, but my browser had cached the `.js` and didn't reload it. Meanwhile 
because my staged version was a new site, it did a fresh load, and the error 
showed up there. Another win for staging.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@tooling.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tooling.apache.org
For additional commands, e-mail: dev-h...@tooling.apache.org

Reply via email to