Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Content-Length on GET request #166

Closed
jarrodek opened this issue Apr 16, 2019 · 0 comments
Closed

Content-Length on GET request #166

jarrodek opened this issue Apr 16, 2019 · 0 comments
Assignees
Labels

Comments

@jarrodek
Copy link
Member

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

  1. The app clears content-* headers when switching from POST to GET
  2. 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

  1. Create a GET request
  2. Add Content-Type header
  3. Add Content-Length header
  4. Run the request. Eventually it renders timeout error.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

No branches or pull requests

1 participant