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.

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

Connection close header error #100

Open
DobromirM opened this issue Jan 12, 2023 · 1 comment · May be fixed by #103
Open

Connection close header error #100

DobromirM opened this issue Jan 12, 2023 · 1 comment · May be fixed by #103
Assignees
Labels
C-bug Category: bug

Comments

@DobromirM
Copy link
Member

When a Connection: close header is sent with a request, the HTTP server closes the connection BEFORE sending the response and then it fails when trying to respond to the closed connection.

According to RFC 2616 the connection should be closed after the response is sent:

HTTP/1.1 defines the "close" connection option for the sender to
signal that the connection will be closed after completion of the
response. For example,

   Connection: close

in either the request or the response header fields indicates that
the connection SHOULD NOT be considered `persistent' (section 8.1)
after the current request/response is complete.

@DobromirM DobromirM added the C-bug Category: bug label Jan 12, 2023
@DobromirM DobromirM assigned DobromirM and unassigned DobromirM Jan 12, 2023
@DobromirM
Copy link
Member Author

This is the code that causes the issue:

@DobromirM DobromirM linked a pull request Jan 12, 2023 that will close this issue
@DobromirM DobromirM self-assigned this Jan 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category: bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant