Open
Description
Version
current git master
Platform
Linux
Description
hyper rejects HTTP responses where the first header has leading whitespace. This is spec compliant.
The popular browsers accept such headers and therefore we are now converting curl to (again) also allow them (in curl/curl#11607).
hyper's current behavior prevents it from getting content other widely used HTTP clients can fetch. Do you think that is perhaps reason to reconsider this stance and allow this violation? It would make life in curl easier as right now curl+hyper builds have different behavior than curl with its native HTTP implementation.
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
Cause Known