Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] MQTT 5: max payload size response #93

Closed
dmytro-landiak opened this issue Jan 2, 2024 · 0 comments
Closed

[Bug] MQTT 5: max payload size response #93

dmytro-landiak opened this issue Jan 2, 2024 · 0 comments
Assignees
Labels
Bug Something isn't working

Comments

@dmytro-landiak
Copy link
Contributor

Describe the bug

When the MQTT 5 client is connecting, the wrong Maximum Packet Size is returned. Based on the code, the min value between tcp and ssl listeners is returned:

Math.min(tcpMaxPayloadSize, sslMaxPayloadSize)).

In this way, if the ssl communication is used and tcp has lower value, then this lower value is returned for ssl but it should be greater.

The correct behavior is when the single max payload size can be set for all listeners or separate ones for each of them.

Your Server Environment

  • TBMQ version: [1.2.1]
@dmytro-landiak dmytro-landiak added the Bug Something isn't working label Jan 2, 2024
@dmytro-landiak dmytro-landiak added this to the 1.2.2 milestone Jan 2, 2024
@dmytro-landiak dmytro-landiak self-assigned this Jan 2, 2024
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant