You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Volley caches POST requests by default. But the semantics for doing so are pretty broken - the request body is not included in the default cache key and POST requests are always supposed to hit the origin server according to the RFC - the cached response should only be used for subsequent GET requests in certain scenarios (e.g. https://www.mnot.net/blog/2012/09/24/caching_POST).
Unless/until we have an actual implementation of a working POST cache by default, we should disable this functionality and leave it up to clients to implement or turn on if it's really what they want.
The text was updated successfully, but these errors were encountered:
Original context: #154
Volley caches POST requests by default. But the semantics for doing so are pretty broken - the request body is not included in the default cache key and POST requests are always supposed to hit the origin server according to the RFC - the cached response should only be used for subsequent GET requests in certain scenarios (e.g. https://www.mnot.net/blog/2012/09/24/caching_POST).
Unless/until we have an actual implementation of a working POST cache by default, we should disable this functionality and leave it up to clients to implement or turn on if it's really what they want.
The text was updated successfully, but these errors were encountered: