Skip to content

Don't forward CloseAbnormalClosure(1006) and CloseTLSHandshake(1015) as close frames#25

Open
ttjiaa wants to merge 1 commit into
koding:masterfrom
ttjiaa:improved-close-frame-handling
Open

Don't forward CloseAbnormalClosure(1006) and CloseTLSHandshake(1015) as close frames#25
ttjiaa wants to merge 1 commit into
koding:masterfrom
ttjiaa:improved-close-frame-handling

Conversation

@ttjiaa

@ttjiaa ttjiaa commented Jul 27, 2018

Copy link
Copy Markdown
Contributor

This PR fixes the issue where CloseAbnormalClosure(1006) and CloseTLSHandshake(1015) are incorrectly forwarded as close frames, as they are reserved.

Changes are made in correspondence to https://github.com/vulcand/oxy/blob/master/forward/fwd.go#L402-L418.

Ref: https://developer.mozilla.org/en-US/docs/Web/API/CloseEvent

@seriousben seriousben left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Thanks, this will fix chrome complaining about reserved close code being sent.

@feiyiban

Copy link
Copy Markdown

The problem still exists

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants