3 ms·
Hmm, 'no-cache' meaning please cache it in reality may have been the problem in the past why those damn internet explorers cached ajax responses and the only wa
by tpetry 6y ago
Hmm, 'no-cache' meaning please cache it in reality may have been the problem in the past why those damn internet explorers cached ajax responses and the only way to solve it was to append a random query parameter?
- s3cur3 6y agoReading that, I finally understood so many hours of debugging throughout my life.
- DangerousPie 6y agoSeems like one of those strings you could search Github for to find thousands of bugs at once.
- pas 6y agoIt sends a revalidation request, so unlikely in theory, but probably many [shared] hosting providers set up a forced cache on server side ... or otherwise the server-side was wrong. (After all if someone used no-cache instead of no-store maybe they mucked up something else too.)