Skip to content

HTTP Parse Error if Response is using transfer-encoding chunked, but includes a content-length header #7136

@kurtnordstrom

Description

@kurtnordstrom
  • v6.2.0:
  • 4.2.0-36-generic rename node.js -> io.js #42~14.04.1-Ubuntu SMP Fri May 13 17:27:22 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux:
  • Subsystem:

In the rare case that nodejs is acting as an http client and the server returns a response that is in Transfer-Encoding: Chunked format, but (for whatever reason), also includes a Content-Length header, node will throw a Parse Error.

Proper behavior, as per RFC2616 would be to discard the Content-Length header if present alongside Transfer-Encoding: Chunked.

Metadata

Metadata

Assignees

No one assigned

    Labels

    httpIssues or PRs related to the http subsystem.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions