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

Allow authorizing channels which are connected through LocalAddress #390

Merged
merged 1 commit into from
Jan 11, 2017
Merged

Allow authorizing channels which are connected through LocalAddress #390

merged 1 commit into from
Jan 11, 2017

Conversation

danwue
Copy link

@danwue danwue commented Aug 16, 2016

Local addresses (io.netty.channel.local.LocalAddress) are quite useful as they don't bind to real socket address are less likely to cause unwanted side-effects with other processes for integration tests and unit tests.
Authorization for socket io clients connecting through local address failed because HandshakeData data was expecting instance of InetSocketAddress.

…el.local.LocalAddress

Local addresses (io.netty.channel.local.LocalAddress) are quite useful as they don't bind to real socket address are less likely to cause unwanted side-effects with other processes.
Authorization for socket io clients connecting through local address failed because HandshakeData data was expecting instance of InetSocketAddress.
@kshchepanovskyi
Copy link

@mrniko can you please also make a release with this fix :)

@kshchepanovskyi
Copy link

@mrniko can you please take a look at this PR?

@mrniko mrniko merged commit 341c0b0 into mrniko:1.6 Jan 11, 2017
@mrniko
Copy link
Owner

mrniko commented Jan 11, 2017

@kshchepanovskyi Done! Thank you

@mrniko mrniko added this to the 1.7.13 milestone Jan 11, 2017
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.

None yet

3 participants