Re: [whatwg/fetch] Proposal: Support GET bodies (#83)

I too agree that GET should support bodies.   This used to be supported back in 2012 to 2014; but now it isn't any more.  You guys do know that there is a limit on how lone the URL can be?  Be cause of this limitation, we need to be able to pass data for a HTTP GET via the request body.  Per the HTTP Status codes, the HTTP GET does not say you can't pass data via the Request body; so I don't know why this implementation is so limiting.  Lastly there are a lot of other frameworks that interpret the specification this way too.  Please reconsider and allow for HTTP GET to send Request body.  It kind of stupid to have to do an HTTP POST when all we really want to do is HTTP GET.  I guess it also comes down to semantics; as we don't want to do a POST unless we are actually save/changing state of some server resource.  We want to be a HTTP GET when we want to retrieve resource/data from the server.  We need to send Request body here because the query parameter may be too long for the URL.

Thank you.

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