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

Deprecate old websocket specs #1160

Closed
fafhrd91 opened this issue Sep 12, 2016 · 5 comments
Closed

Deprecate old websocket specs #1160

fafhrd91 opened this issue Sep 12, 2016 · 5 comments
Labels
outdated
Milestone
2.0

Comments

@fafhrd91
Copy link
Member

it seems we don't really need SEC_WEBSOCKET_KEY1 header support
@asvetlov
Copy link
Member

Sorry, I don't follow.

@fafhrd91
Copy link
Member Author

Search it in source code

Sent from my iPhone

On Sep 13, 2016, at 4:30 AM, Andrew Svetlov notifications@github.com wrote:

Sorry, I don't follow.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@asvetlov
Copy link
Member

Sorry, I still don't understand you.
What concrete actions should be done for fixing your request?

@fafhrd91
Copy link
Member Author

SEC_WEBSOCKET_KEY1 is from old websocket spec, it is not used anymore.

@fafhrd91 fafhrd91 added this to the 1.5 milestone Feb 8, 2017
@fafhrd91 fafhrd91 changed the title remove support for SEC_WEBSOCKET_KEY1 Deprecate old websocket specs Feb 8, 2017
@fafhrd91 fafhrd91 modified the milestones: 2018-01-01 Deprecations, 1.5 Feb 8, 2017
@fafhrd91 fafhrd91 modified the milestones: 1.4, 2018-01-01 Deprecations Feb 16, 2017
@aio-libs-bot aio-libs-bot mentioned this issue Oct 3, 2018
Closed
@lock
Copy link

lock bot commented Oct 29, 2019

This thread has been automatically locked since there has not been
any recent activity after it was closed. Please open a new issue for
related bugs.

If you feel like there's important points made in this discussion,
please include those exceprts into that new issue.

@lock lock bot added the outdated label Oct 29, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Oct 29, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
outdated
Projects
None yet
Milestone
2.0
Development

No branches or pull requests
2 participants
@asvetlov @fafhrd91