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

return 'connection: close' header in response #721

Merged

Conversation

RmStorm
Copy link
Contributor

@RmStorm RmStorm commented Jul 23, 2020

According to https://www.w3.org/Protocols/rfc2616/rfc2616-sec8.html a
server should return the 'connection: close' header in the response when
a request has that header. Resolves #720

@RmStorm RmStorm force-pushed the fix/return-connection-close-header-to-client branch 2 times, most recently from 85c327b to ffb0b2b Compare July 24, 2020 06:53
@euri10 euri10 added the http label Dec 28, 2020
@RmStorm RmStorm force-pushed the fix/return-connection-close-header-to-client branch from ffb0b2b to 00e5100 Compare January 25, 2021 07:42
According to https://www.w3.org/Protocols/rfc2616/rfc2616-sec8.html a
server should return the 'connection: close' header in the response when
a request has that header. Resolves encode#720
Copy link
Member

@euri10 euri10 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks @RmStorm !

@euri10 euri10 merged commit bd1a096 into encode:master Jan 25, 2021
@euri10 euri10 mentioned this pull request Feb 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

connection: close header not returned in response
2 participants