I built cachewhy around a small but costly HTTP cache mistake. Imagine a request for /missing.js that returns 404 with Cache-Control: public, max-age=2678400. That lifetime is 31 days. A browser may reuse the missing response even after the file is deployed. Changing the server header helps new responses, but it does not automatically erase a copy... Weiterlesen: Why a missing JavaScript file can stay missing after you deploy it
Intelligence View
⚡ tsecurity.de Intelligence
Why a missing JavaScript file can stay missing after you deploy it
I built cachewhy around a small but costly HTTP cache mistake. Imagine a request for /missing.js that returns 404 with Cache-Control: public, max-age=2678400.…