Hello, I believe that I found a bug in the Qpid C++ broker (I tried versions 1.35 and 1.36 and both are affected). When the broker is configured to use the DIGEST-MD5 SASL mechanism, the authentication passes successfully, but just after that the broker issues a completely invalid AMQP 1.0 frame. As a result, the client complains about a framing error and disconnects. I am using a client based on python-qpid-proton 0.16.0 but that should not be important I guess. When I change the SASL mechanism to CRAM-MD5, PLAIN or ANONYMOUS, everything works well.
Attached is a tcpdump file with four subsequent connection attempts, showing the described behavior: amqp.dmp <http://qpid.2158936.n2.nabble.com/file/n7657354/amqp.dmp> Regards, Pavel -- View this message in context: http://qpid.2158936.n2.nabble.com/Qpid-C-1-36-issues-an-invalid-AMQP-1-0-frame-after-successful-DIGEST-MD5-authentication-tp7657354.html Sent from the Apache Qpid users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
