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
When switching from POST to GET requests the app does not filters headers list for payload specific values (Content-Type, Content-Length, other Content-* headers). This causes timeout error as the server is waiting for the data from the client but none arrives as the transport library clears payload for GET, HEAD.
Expected Behavior
The app clears content-* headers when switching from POST to GET
The app warns the user about potentially unwanted headers
I would suggest option 2 as altering request data on behalf of the user should not be practiced. It would help unexperienced users but would eliminate some test scenarios for advanced users.
Actual behavior
The server waits for the data from the client until timeout and the client closes the connection with 0 status code.
To Reproduce
Create a GET request
Add Content-Type header
Add Content-Length header
Run the request. Eventually it renders timeout error.
The text was updated successfully, but these errors were encountered:
When switching from POST to GET requests the app does not filters headers list for payload specific values (Content-Type, Content-Length, other Content-* headers). This causes timeout error as the server is waiting for the data from the client but none arrives as the transport library clears payload for
GET
,HEAD
.Expected Behavior
POST
toGET
I would suggest option 2 as altering request data on behalf of the user should not be practiced. It would help unexperienced users but would eliminate some test scenarios for advanced users.
Actual behavior
The server waits for the data from the client until timeout and the client closes the connection with 0 status code.
To Reproduce
The text was updated successfully, but these errors were encountered: