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
WebSocketServerHandshaker::handshake returns a Future that is never completed if HTTP request is not a FullHttpRequest #12655
Comments
A workaround is to put a HttpObjectAggregator to the channel's initial pipeline. If it is added in the channel initializer, then the handshaking future will be completed after the handshake is done. |
hoat4
changed the title
WebSocketServerHandshaker::handshake returns a Promise that is never completed if HTTP request is not a FullHttpRequest
WebSocketServerHandshaker::handshake returns a Future that is never completed if HTTP request is not a FullHttpRequest
Jul 28, 2022
@hoat4 Hi, i'll take a look. |
chrisvest
pushed a commit
that referenced
this issue
Aug 1, 2022
@amizurov what is the status of this one ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected behavior
The FutureListener should be invoked when the WS handshake is done.
Actual behavior
The handshake completes successfully, but the FutureListener associated with handshaking is not invoked (but the next ChannelHandlerAdapter receives the WS message correctly).
Steps to reproduce
Run the code below. If you connect to it, the "Handshake done" string won't print, but the received messages will be printed.
Minimal yet complete reproducer code (or URL to code)
Netty version
5.0.0.Alpha4
JVM version (e.g.
java -version
)17
OS version (e.g.
uname -a
)Windows 11
The text was updated successfully, but these errors were encountered: