GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
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?
to your account
Sola opened SPR-17547 and commented
Currently, both server-side and client-side on the Reactive stack cannot get CloseStatus when the other side actively closes the connection.
the CloseStatus can be useful when the remote closes with a reasonable reason.
Rossen Stoyanchev commented
Scheduling for 5.2, but for Reactor Netty we'll also need a way to get it from the WebsocketInbound. I've created reactor/reactor-netty#533.
David Terk commented
Could #21790 be related to this if the server is closing the connection?
This ticket is for a WebSocket session. #21790 is for an HTTP POST. I don't see how they could be related.
Sorry Rossen Stoyanchev I missed that this was specific to WebSocket.
the original reporter here.
Looks like this is no longer blocked as of Reactor Netty 0.9.