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
Since GET requests do not have a body -- request data is instead encoded in the query string -- the client should not send content headers (such as content-length, content-type, content-encoding). Server should not allow a GET requests that does include a non-empty body.
The client in this repo is including content-type headers and the server is not confirming that the body is empty for GET requests.
Found by conformance tests in v1.12.0.
The text was updated successfully, but these errors were encountered:
Since GET requests do not have a body -- request data is instead encoded in the query string -- the client should not send content headers (such as content-length, content-type, content-encoding). Server should not allow a GET requests that does include a non-empty body.
The client in this repo is including content-type headers and the server is not confirming that the body is empty for GET requests.
Found by conformance tests in v1.12.0.
The text was updated successfully, but these errors were encountered: