Provide access to the WebSocket close status in WebFlux

[spring-projects-issues]

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.

---

Affects: 5.1.3

[spring-projects-issues]

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.

[spring-projects-issues]

David Terk commented

Rossen Stoyanchev

Could #21790 be related to this if the server is closing the connection?

[spring-projects-issues]

Rossen Stoyanchev commented

This ticket is for a WebSocket session. #21790 is for an HTTP POST. I don't see how they could be related.

[spring-projects-issues]

David Terk commented

Sorry Rossen Stoyanchev I missed that this was specific to WebSocket.

[unlimitedsola]

the original reporter here.

[rstoyanchev]

Looks like this is no longer blocked as of Reactor Netty 0.9.

[Fetsivalen]

Hi,
Is anyone working on this issue?

I'd like to contribute it to the ReactorNettyWebSocketSession,
but I wonder is this ticket is about ReactorNetty's implementation only, or it is about all implementations of the WebSocketSession (not sure that each implementation will give such a possibility)?

[rstoyanchev]

ReactorNettyWebSocketSession is the starting point but we'd want to expose it on WebSocketSession since that's what an application is typically using. From there it will need to be implemented across but all other servers make this available in their API.

Short answer is yes for all implementations.