3 ms·

So to clarify, the problem is that browser serves the cached copy of the response from the GET request to the user, meaning that the user will not see the possi

So to clarify, the problem is that browser serves the cached copy of the response from the GET request to the user, meaning that the user will not see the possibly different response returned by the server for the DELETE request correct? I feel like I'm missing something here.

darklajid 14y ago
No, the browser doesn't actually send the DELETE in the first place..
- corford 14y ago
  Just to be clear (because I feel like I'm missing something here as well): the problem is if you allow a GET to be cached and then the client makes a DELETE request on that cached resource, Chrome applies the DELETE to the cached version and doesn't propagate the request to the server??
  - eranation 14y ago
    From the logs it seems to me it doesn't do a DELETE and sends a "GET (from cache)" type of request