Currently it's not possible to utilize any custom headers sent via STOMP connect command (for example custom authentication data). This is due to the fact that connectToProxiedTarget doesn't accept WebSocketMessageAccessor as other command methods do.
Currently it's not possible to utilize any custom headers sent via STOMP connect command (for example custom authentication data). This is due to the fact that
connectToProxiedTarget
doesn't acceptWebSocketMessageAccessor
as other command methods do.