Skip to content

spec. compliance regarding transfer-encoding headers #1883

@uNetworkingAB

Description

@uNetworkingAB

There is non-standard interpretation of, for instance, two "transfer-encoding" headers. This should be added in h1spec test, and fixed.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions