Chrome even caches HTTP DELETE requests
Aggressive content caching by the Chrome browser has become an anecdote and the subject of headaches for web developers. How far is Chrome ready to go in resource caching? The answer: very far. Up to the point that he even handles the removal request for a resource from the cache .
To reproduce the bug, you must first send a request to the REST service with a caching header.
The following resource deletion request:
In the bug tracker Chromium, a funny discussion has unfolded: they say that Google does not believe that something can be removed from the Internet.
To reproduce the bug, you must first send a request to the REST service with a caching header.
Request URL: http://localhost:8888/files/cat.jpg Request Method: GET Status Code: 200 OK Response Headers Cache-Control:max-age=3600 The following resource deletion request:
Request URL:http://localhost:8888/files/cat.jpg Request Method:DELETE Status Code:200 OK (from cache) In the bug tracker Chromium, a funny discussion has unfolded: they say that Google does not believe that something can be removed from the Internet.
')
Source: https://habr.com/ru/post/148779/
All Articles