8000 connection: close header not returned in response · Issue #720 · encode/uvicorn · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
connection: close header not returned in response #720
Closed
@RmStorm

Description

@RmStorm

Hello, the W3 standard seems to say that a server which receives a request with a connection: close header should also return this header to the client. Specifically I'm talking about the first line in 8.1.2.1 Negotiation quoted here:

An HTTP/1.1 server MAY assume that a HTTP/1.1 client intends to maintain a persistent connection unless a Connection header including the connection-token "close" was sent in the request. If the server chooses to close the connection immediately after sending the response, it SHOULD send a Connection header including the connection-token close.

The wording is maybe a little ambiguous but to me it definitely seems to imply that if the server closes the connection (wether due to a connection: close header in the request or by it's own choice) it should return a connection: close header. I ran into an issue with the asks library were this was causing an issue: theelous3/asks#115.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0