You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Preface:
From https://tools.ietf.org/html/rfc7230
"A user agent SHOULD NOT send a Content-Length header field when the request message does not contain a payload body and the method semantics do not anticipate such a body."
The issue:
Even if the following thing would be (logically) incorrect, it's still allowed to be done:
In this case, the payload passed to the "send" method will not be converted into a query string, and the "content-length" header will be added to the GET request.
This might cause the request to be rejected by web services.
Preface:
From https://tools.ietf.org/html/rfc7230
"A user agent SHOULD NOT send a Content-Length header field when the request message does not contain a payload body and the method semantics do not anticipate such a body."
The issue:
Even if the following thing would be (logically) incorrect, it's still allowed to be done:
In this case, the payload passed to the "send" method will not be converted into a query string, and the "content-length" header will be added to the GET request.
This might cause the request to be rejected by web services.
The issue is reproduced here: https://repl.it/@MarcelloBarile/superagent-content-length
The text was updated successfully, but these errors were encountered: