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

Unnecessary Content-Type and Content-Length headers are included with GET requests #5

Open
pvsr opened this issue Jan 22, 2025 · 0 comments · May be fixed by #6
Open

Unnecessary Content-Type and Content-Length headers are included with GET requests #5

pvsr opened this issue Jan 22, 2025 · 0 comments · May be fixed by #6

Comments

@pvsr
Copy link

pvsr commented Jan 22, 2025

Currently all GET requests from gleam_hackney include Content-Type and Content-Length headers, even when the body is empty (in which case they're application/octet-stream and 0 respectively, defaults from hackney). RFC 9110 says " A user agent SHOULD NOT send a Content-Length header field when the request message does not contain content and the method semantics do not anticipate such data." Most sites probably handle it fine but I ran into one page that responds to any GET having a non-empty Content-Length with a 500.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant