-
Notifications
You must be signed in to change notification settings - Fork 647
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
No way to receive close status with WebSocketInbound #533
Labels
type/enhancement
A general enhancement
Milestone
Comments
One idea to consider, an extra method in
|
OlegDokuka
added a commit
to OlegDokuka/reactor-netty
that referenced
this issue
Aug 15, 2019
OlegDokuka
added a commit
to OlegDokuka/reactor-netty
that referenced
this issue
Aug 15, 2019
Signed-off-by: Oleh Dokuka <[email protected]>
OlegDokuka
added a commit
to OlegDokuka/reactor-netty
that referenced
this issue
Sep 1, 2019
Signed-off-by: Oleh Dokuka <[email protected]>
OlegDokuka
added a commit
to OlegDokuka/reactor-netty
that referenced
this issue
Sep 1, 2019
Signed-off-by: Oleh Dokuka <[email protected]>
OlegDokuka
added a commit
to OlegDokuka/reactor-netty
that referenced
this issue
Sep 1, 2019
Signed-off-by: Oleh Dokuka <[email protected]>
violetagg
pushed a commit
that referenced
this issue
Sep 1, 2019
Signed-off-by: Oleh Dokuka <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
WebsocketInbound
providesFlux<WebSocketFrame> receiveFrames()
which turnsCloseWebSocketFrame
into a completion signal, but a result there is no way to receive the close status and reason sent by the remote peer. This is asymmetric withWebSocketOutbound
which does provide a way to send a close status and reason.This same has been requested in SPR-17547 but in order to implement it there, we'd first need a way to get the close status through the Reactor Netty API.
The text was updated successfully, but these errors were encountered: