[whatwg/fetch] Why does the Fetch standard forbid GET Body when it's not against REST? (Issue #1644)

The REST standard, updated 2014,  RFC 7231 https://www.rfc-editor.org/rfc/rfc7231 ; basically the 2014 spec for REST says that a body for a GET statement should not be predefined by software operating it, and not excluded. "A payload within a GET request message has no defined semantics."  There is a decent Stackoverflow thread about it here: https://stackoverflow.com/a/983458

Why do the Fetch specs then forbid it? https://fetch.spec.whatwg.org/#dom-request

I realize it's easily accomplished, encoding json into URL parameters. However I'd like to understand the appetite for divergence on this issue.

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

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