support message-body in get requests

[jochen42]

rfc7231 does not forbit sending payload with GET-Requests. In several cases this is needed because of the size-restriction on GET-Parameters.

fixes #787

[lean1024]

PR? and why again did i recieve this message? ^ ^ Am Do., 25. Apr. 2019 um 15:23 Uhr schrieb shelru <notifications@github.com

…

: @rubennorte <https://github.com/rubennorte> related to #787 (comment) <#787 (comment)> Can you accept PR 2 year's later? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1912 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHZKWEJHILW6HZW2TNRQLRLPSGWD7ANCNFSM4GIZIO5A> .

[afwn90cj93201nixr2e1re]

https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest/send @jochen42
If the request method is GET or HEAD, the body parameter is ignored and the request body is set to null.
Did you check is it work?

[lean1024]

well, i remember asking it in the context of elasticsearch and trying to send a Get Request with a body was not supported of axios.. so that was my problem since all examples of elasticsearch were Get Request with a body turns out - you can fire the elastic api with Post request and Body and it handles it :P hidden information Am Do., 25. Apr. 2019 um 16:14 Uhr schrieb shelru <notifications@github.com

…

: https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest/send @jochen42 <https://github.com/jochen42> If the request method is GET or HEAD, the body parameter is ignored and the request body is set to null. Did you check is it work? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1912 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHZKWEMZUKNUWSIQUJ6YEILPSG4FJANCNFSM4GIZIO5A> .

[jochen42]

https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest/send @jochen42
If the request method is GET or HEAD, the body parameter is ignored and the request body is set to null.
Did you check is it work?

@afwn90cj93201nixr2e1re: no i did not tested it in mozilla/firefox. only chrome. (we had an heterogene environment in the project - only chrome/chromium as browser). but i think if mozilla documents it like this, a merge doesn't make sense, because of compatibility.

feel free to cancel/decline the pr.