“This specification defines a new HTTP method, QUERY, as a safe, idempotent request method that can carry request content.”: https://www.ietf.org/archive/id/draft-ietf-httpbis-safe-method-w-body-05.html
-
“This specification defines a new HTTP method, QUERY, as a safe, idempotent request method that can carry request content.”: https://www.ietf.org/archive/id/draft-ietf-httpbis-safe-method-w-body-05.html
-
(Note: This is just an Internet-Draft, an idea thrown up for discussion. But, an interesting one.)
-
@timbray I like it.
In fact, I was just thinking this morning how much I'd like to be able to include POST-style content with a GET request, just to make more complicated queries feasible. -
@timbray interesting
A few immediate thoughts/questions (some may be simplistic)
- is it safe to assume that any standards suggested as HTTP would also work with HTTPS? (Seems like you want that layer of security here especially)
- I imagine there should be some way to limit access to Query requests - ie authentication or to at least impose limits (ie 10 results is ok but a request for 10M requests might not be)
- pagination or some form of sequencing might be useful (ie next 10 results)
-
@KatS @timbray Isn't that essentially a form post, with the type set to GET? It's all pretty abstract anyways if you watch what's really going on on most web servers: get, post, delete, patch.... not sure why a "query" is different than a "get". It's not like you are going to take a raw SQL query and pass it on... are you.. ARE YOU?
-