Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Content-Length request header should be honored #1440

Closed
slandelle opened this issue Jul 25, 2017 · 0 comments
Closed

Content-Length request header should be honored #1440

slandelle opened this issue Jul 25, 2017 · 0 comments
Assignees
@slandelle
Labels
Defect
Milestone
2.1.0

Comments

@slandelle
Copy link
Contributor

slandelle commented Jul 25, 2017 •
edited
Loading

User defined Content-Length request header should have precedence over the one from the body, all the more when it's undefined and we fall back to chunked transfer-encoding.
@slandelle slandelle self-assigned this Jul 25, 2017
@slandelle slandelle added this to the 2.1.0 milestone Jul 25, 2017
@slandelle slandelle changed the title Content-Length header should be honored when passing an InputStream Content-Length request header should be honored Jul 25, 2017
slandelle added a commit that referenced this issue Jul 25, 2017
@slandelle
User defined Content-Length request header should be honored, close #…
1d8a630 
…1440

Motivation:

When Content-Length is known beforehand, we shouldn’t ignore it and
enforce chunked transfer-encoding.

Modification:

Honor Content-Length request header when it's defined.

Result:

Chunked transfer-encoding is no longer enforced
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@slandelle slandelle

Labels
Defect
Projects
None yet
Milestone
2.1.0
Development

No branches or pull requests
1 participant
@slandelle