-
Notifications
You must be signed in to change notification settings - Fork 817
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
New configuration parameter : setting the HandshakeTimeout on SslHandler #531
Labels
Comments
dsoulayrol
pushed a commit
to dsoulayrol/moquette
that referenced
this issue
Nov 5, 2020
dsoulayrol
pushed a commit
to dsoulayrol/moquette
that referenced
this issue
Nov 13, 2020
Hi. I have to freeze and package a product in a few days which needs this feature. I need to know if I have a chance to see this request soon merged so as to rely on the main repository of moquette, or if I have to generate my own version. Thanks. |
dsoulayrol
pushed a commit
to dsoulayrol/moquette
that referenced
this issue
May 4, 2021
dsoulayrol
pushed a commit
to dsoulayrol/moquette
that referenced
this issue
Feb 8, 2023
dsoulayrol
pushed a commit
to dsoulayrol/moquette
that referenced
this issue
Apr 14, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I am working with embedded devices which are very limited in resources, and the server certificate verification takes a very long time. The server closes the connection after 10 seconds, far before the client has completed its computation to ask for the key exchange.
This timeout is set by
io.netty.handler.ssl.SslHandler
. This handler is created inNewNettyAcceptor#createSslHandler
. (I am using version 0.12.1, but I see nothing changed in master). When I callSslHandler#setHandshakeTimeoutMillis
here, my problem is solved.So I'd like to have the capability to provide this timeout value as a property for moquette. I believe it would be an interesting feature because MQTT is easily used on embedded devices, and SSL support is somewhat heavy, so my problem could be seen elsewhere.
I am ready to create a Pull Request if necessary, but I would be happy to hear your comments first on the subject.
The text was updated successfully, but these errors were encountered: