Re:HTTP/1.1 just got a major update
by dragonwriter on Saturday June 07, 2014 @12:26PM
(#7862396)
> Instead of just using the URL as the caching key, use URL+body. Same URL and same body = same response.
Well, except that since the body isn't defined as having semantics that determine the response, an cache based on the HTTP protocol spec has no reason to do that.
Re:HTTP/1.1 just got a major update
by ajanuary on Sunday June 08, 2014 @06:50AM
(#7864396)
Talking from a practical standpoint, to try and have GET requests with large parameters you could put the data in the message body, and then a hash of the message in the URL to avoid caching issues.
Well, except that since the body isn't defined as having semantics that determine the response, an cache based on the HTTP protocol spec has no reason to do that.