4 ms·
I'm getting 403 errors on a range [1] of CSS and Js files: Can someone elaborate as to why this would be a 403 [2] error as opposed to maybe a 401? [1] https:
by mjsweet 4y ago
I'm getting 403 errors on a range [1] of CSS and Js files:
Can someone elaborate as to why this would be a 403 [2] error as opposed to maybe a 401?
[1] https://imgur.com/gallery/nWteVUn https://imgur.com/gallery/nWteVUn
[2] https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/403 https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/403
- classified 4y agoThose files matched a CSAM hash.
- rovr138 4y ago403, Forbidden, implies permissions. 401, Unauthorized, implies authentication (credentials).
- derefr 4y agoProbably baked as a static site, uploaded to an object-storage bucket, fronted with a CDN. Object storage providers (first AWS, but then copied elsewhere) serve 403 instead of 404 when an object doesn't exist in the bucket, to truly hide objects that users don't have access to, by making "unauthorized" indistinguishable from "doesn't exist."