Skip to content
This repository has been archived by the owner on Dec 18, 2018. It is now read-only.

Handle non "chunked" Transfer-Encoding request header values. #1181

Closed
halter73 opened this issue Oct 25, 2016 · 0 comments
Closed

Handle non "chunked" Transfer-Encoding request header values. #1181

halter73 opened this issue Oct 25, 2016 · 0 comments
Assignees
@cesarblum
Labels
3 - Done bug
Milestone
1.1.0

Comments

@halter73
Copy link
Member

Kestrel currently assumes that the request is chunked if the Transfer-Encoding request header is present. This may not be the case.
@halter73 halter73 mentioned this issue Oct 25, 2016
Merged
@cesarblum cesarblum self-assigned this Oct 26, 2016
@cesarblum cesarblum added this to the 1.1.0 milestone Oct 26, 2016
cesarblum pushed a commit that referenced this issue Oct 27, 2016
Properly handle tokens in Transfer-Encoding response header (#1181).
7262529
@cesarblum cesarblum mentioned this issue Oct 27, 2016
Merged
cesarblum pushed a commit that referenced this issue Oct 31, 2016
Properly handle tokens in Transfer-Encoding response header (#1181).
cb925d4
cesarblum pushed a commit that referenced this issue Oct 31, 2016
Handle tokens in Transfer-Encoding header (#1181).
2940895
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@cesarblum cesarblum

Labels
3 - Done bug
Projects
None yet
Milestone
1.1.0
Development

No branches or pull requests
2 participants
@halter73 @cesarblum