Kevin Berendsen
bc6525e431
MQTT3.1.3-6 stated that the client can connect without giving up an client identifier. However, the broker should generate one for the client id as of the client gave the identifier to broker. The client will now disconnect if the client hasn't given up an identifier with clean session set to 0. Done this regarding issue #190
...
NettyChannelAssertions class has been modified so you could add a message to the assertion.
Unit tests have been added to test the modified processConnect() method.
The server can allow zero byte client identifiers through moquette configuration.
2016-08-07 13:17:41 +02:00
andsel
f7466fd968
Added check to avoid creation of LostConnectionEvents for not yet completed connects (fix issue #88 )
2015-09-22 15:29:23 +02:00
andrea
29bdd2f8fb
Modified the format of password_file.conf now accept only sha256 hashed passwords
2015-05-13 22:25:05 +02:00
andrea
9d8e9df44e
Added handling of allow_anonymous, fix issue #34
2015-04-25 19:49:41 +02:00
selva.andre
6755723e0b
Added websocket connector
2014-05-18 12:02:18 +02:00
andrea
1ad5acef7c
Added loading of user identities form password_file, Fix issue #23
2014-03-02 18:16:50 +01:00