Skip to content

Option to allow leading whitespace in first HTTP/1 response header #3285

Open
@bagder

Description

@bagder

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

No one assigned

    Labels

    A-clientArea: client.A-http1Area: HTTP/1 specific.B-upstreamBlocked: needs a change in a dependency or the compiler.C-featureCategory: feature. This is adding a new feature.E-easyEffort: easy. A task that would be a great starting point for a new contributor.

    Type

    No type

    Projects

    Status

    Cause Known

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions