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
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.
The text was updated successfully, but these errors were encountered:
Currently all GET requests from gleam_hackney include
Content-Type
andContent-Length
headers, even when the body is empty (in which case they'reapplication/octet-stream
and0
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-emptyContent-Length
with a 500.The text was updated successfully, but these errors were encountered: