You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It emits a few more CONNECT frames interspersed with normal operation before eventually crashing with the error message Unexpected response received. Expected a "CONNECTED" Frame to determine Version. Got a "Message" Frame
If session and server headers are supplied, this behaviour isn't exhibited, and it works fine.
session is ambiguously defined in 1.0, it could be interpreted as being required, but in all future versions, all headers except version are optional in CONNECTED.
The text was updated successfully, but these errors were encountered:
I don't know what selenetherium is, is that a client or server built using stomp-php? Just trying to understand the issue here and on what side stomp-php is on.
Hi @whikloj, not the clearest explanation on my part, selenetherium is a server. In the logs, all client frames came from stomp-php, and all server frames from selenetherium. I wrote Selenetherium as a client tester to help me build a list of compatible STOMP clients on the NROD wiki.
To describe the bug here more (hopefully) more exactly, stomp-php expects a CONNECTED frame from a broker to have server and session headers under STOMP 1.1, even though only version is actually required.
This may be helpful as there are parts of this codebase that are less clear to me. So I'm compiling selenetherium, but as I'm not an Erlang developer can you tell me how to get it running and if it is possible to limit the tests run to specific ones?
If selenetherium doesn't supply
session
andserver
headers in its CONNECTED frame:It emits a few more CONNECT frames interspersed with normal operation before eventually crashing with the error message
Unexpected response received. Expected a "CONNECTED" Frame to determine Version. Got a "Message" Frame
If
session
andserver
headers are supplied, this behaviour isn't exhibited, and it works fine.session
is ambiguously defined in 1.0, it could be interpreted as being required, but in all future versions, all headers exceptversion
are optional in CONNECTED.The text was updated successfully, but these errors were encountered: