Defining a new HTTP method: HTTP Search (2021)

Re:Defining a new HTTP method: HTTP Search (2021) by NoMoreNicksLeft on Saturday May 27, 2023 @06:52PM (#36099209)

If I send a request body with GET, what modern systems would even have a problem with that? Is there some caching middleware somewhere that I've never heard of or just ignored that will screw it up?

If there was a GET-with-body http verb I'd probably use it at one point or another, but I often wonder where plain GET would start blowing up if I just used it for that.

Honestly, I think rest is a mess, and that everything should just be POST with no values in the url at all.

[ Parent | on HN ]

Re:Defining a new HTTP method: HTTP Search (2021) by fiddlerwoaroof on Saturday May 27, 2023 @08:12PM (#36099798)

GET with a body is pretty useless because the standard doesn’t allow the body to affect the results. So, proxies, browsers, etc. are free to ignore the body when caching results.

[ Parent | on HN ]

Re:Defining a new HTTP method: HTTP Search (2021) by Too on Sunday May 28, 2023 @03:23AM (#36101894)

Quick workaround: GET /search?key=$hash(body)

[ Parent | on HN ]

Re:Defining a new HTTP method: HTTP Search (2021) by ilyazub on Monday May 29, 2023 @07:50AM (#36113036)

Reminds me Google Maps: GET /search?pb=$protobuf_to_string.

[ Parent | on HN ]

Re:Defining a new HTTP method: HTTP Search (2021) by SpaghettiCthulu on Saturday May 27, 2023 @08:16PM (#36099831)

even though most servers support it AFAIK, many clients don't. Many will even silently discard the body when sending a GET request.

[ Parent | on HN ]