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

When a server returns NoContent, reading the response should not hang #436

Closed
hugoduncan opened this issue Apr 6, 2015 · 0 comments
Closed

When a server returns NoContent, reading the response should not hang #436

hugoduncan opened this issue Apr 6, 2015 · 0 comments
Labels
A-server Area: server. C-bug Category: bug. Something is wrong. This is bad!

Comments

@hugoduncan
Copy link
Contributor

When a client makes a request that results in a NoContent status code, the read methods on the repsonse should return an immediate EOF status, rather than blocking.
@seanmonstar seanmonstar added C-bug Category: bug. Something is wrong. This is bad! A-server Area: server. labels Apr 6, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-server Area: server. C-bug Category: bug. Something is wrong. This is bad!
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@seanmonstar @hugoduncan