Skip to content

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

@hugoduncan

Description

@hugoduncan

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-serverArea: server.C-bugCategory: bug. Something is wrong. This is bad!

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions