Defining a new HTTP method: HTTP Search (2021)

Re:Defining a new HTTP method: HTTP Search (2021) by afiori on Saturday May 27, 2023 @03:11PM (#36097341)

I would say that people should be more open to using HTTP in non-REST ways.

Sometimes you want to send a request and receive a response, with arbirtrary restrictions and side effects that suit your cases.

There are a lot of good reason for rest to exists, but also sometime you want to POST /open-garage-door?t=5-minutes and call it a day

[ Parent | on HN ]

Re:Defining a new HTTP method: HTTP Search (2021) by yashap on Sunday May 28, 2023 @12:29AM (#36101137)

Sure, the odd RPC style HTTP call is fine - not everything is cleanly modelled as a resource. But the lack of a clean way to make GET requests with a more complex request payload is simply a wart/shortcoming in the HTTP protocol IMO, and one that’s very correctable. Sucks to have to abandon RESTfulness even when I have a very “clean fit for the resource model” call to make, but the request body is too complex/large for HTTP query params.

[ Parent | on HN ]