- From: Alex Strachan <notifications@github.com>
- Date: Fri, 02 Jun 2023 17:18:02 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Saturday, 3 June 2023 00:18:07 UTC
> Every time I encounter a `GET` endpoint in the wild that accepts a body, I get reminded that this thread exists and there is not a single post here with an objective reason why `GET` shouldn't have a body. More frustrating the language change on the HTTP spec to say "should not" was supposed to be accompanied by a new method `SEARCH` that would explicitly allow a body. Right now we're in a situation where the best practice for when your query params on a `GET` get too long are to... convert it to a semantically incorrect `POST`, use a nonstandard method `SEARCH` or fight with creating something standard compliant in `HTTP` but that errors if anyone tries to use FETCH. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/issues/551#issuecomment-1574478879 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/fetch/issues/551/1574478879@github.com>
Received on Saturday, 3 June 2023 00:18:07 UTC