I faced an error that stomp websocket client can not send a header with backslash. Then I found reason.
StopmEncoder dose not escape headers when CONNECT and CONNECTED frames, to follow the spec below: https://stomp.github.io/stomp-specification-1.2.html#Value_Encoding However, StompDecoder try to unescape when CONNECT and CONNECTED frames.
StopmDecoder should not unescape when CONNECT and CONNECTED frames, because the frames are not escaped.
Comment From: pivotal-cla
@rygh4775 Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.
Comment From: pivotal-cla
@rygh4775 Thank you for signing the Contributor License Agreement!