Re: [whatwg/fetch] Request with GET/HEAD method cannot have body. (#551)

> > 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.

The language change was only due to the WHATWG not wanting to admit they made a mistake so the standard got modified instead. There is nothing more to it.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/551#issuecomment-1576714382
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/issues/551/1576714382@github.com>