News for hackers. Stuff that matters.
Re:Limitations of the GET method in HTTP by dragonwriter on Monday March 02, 2015 @02:47PM (#9133873)
If the request body effects the behavior, they are breaking the semantics of GET and breaking anything (e.g., caching, including local) built around the defined semantics.

There should be a GET-like method that takes a (significant) request body but is otherwise semantically like GET (e.g., safe) -- essentially, it would represent asking for a representation of the result of applying a pure function to the resource identified by the URI rather than asking for a representation of the resource itself.

But no such function currently exists in HTTP/1.1 or any general purpose extension (there are highly-specific things like the SEARCH method, but that's not general purpose the way the base HTTP/1.1 methods and, say, PATCH are.)

Re:Limitations of the GET method in HTTP by TheLoneWolfling on Monday March 02, 2015 @03:04PM (#9133982)
What about if the header included a hash of the content in the request body?
Re:Limitations of the GET method in HTTP by treve on Monday March 02, 2015 @03:27PM (#9134111)
There's a REPORT method that can used with any content-type.
Re:Limitations of the GET method in HTTP by dragonwriter on Monday March 02, 2015 @03:47PM (#9134211)
If you mean the WebDAV one in RFC 3253, its spec (as is usual for WebDAV methods) has some WebDAV specific requirements in it that aren't really appropriate for general use; content-type isn't the only place where problems with generality can be found.

Something like that completely decoupled from WebDAV is basically what I'd like to see.