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

Client Connection Pool wrongly handles HEAD response with body #640

Closed
seanmonstar opened this issue Aug 31, 2015 · 0 comments
Closed

Client Connection Pool wrongly handles HEAD response with body #640

seanmonstar opened this issue Aug 31, 2015 · 0 comments
Assignees
@seanmonstar
Labels
A-client Area: client. C-bug Category: bug. Something is wrong. This is bad!

Comments

@seanmonstar
Copy link
Member

No description provided.

@seanmonstar seanmonstar added C-bug Category: bug. Something is wrong. This is bad! A-client Area: client. servo labels Aug 31, 2015
seanmonstar added a commit that referenced this issue Sep 1, 2015
@seanmonstar
fix(client): be resilient to invalid response bodies
b42e61f 
When an Http11Message knows that the previous response should not
have included a body per RFC7230, and fails to parse the following
response, the bytes are shuffled along, checking for the start of the
next response.

Closes #640
@seanmonstar seanmonstar self-assigned this Sep 1, 2015
@seanmonstar seanmonstar mentioned this issue Sep 1, 2015
Merged
seanmonstar added a commit that referenced this issue Sep 1, 2015
@seanmonstar
fix(client): be resilient to invalid response bodies
75c7117 
When an Http11Message knows that the previous response should not
have included a body per RFC7230, and fails to parse the following
response, the bytes are shuffled along, checking for the start of the
next response.

Closes #640
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@seanmonstar seanmonstar

Labels
A-client Area: client. C-bug Category: bug. Something is wrong. This is bad!
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@seanmonstar