-
Notifications
You must be signed in to change notification settings - Fork 3k
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
ssl: Correct middle_box negotiation #6249
ssl: Correct middle_box negotiation #6249
Conversation
CT Test Results 2 files 64 suites 48m 19s ⏱️ Results for commit 05ea2d2. ♻️ This comment has been updated with latest results. To speed up review, make sure that you have read Contributing to Erlang/OTP and that all checks pass. See the TESTING and DEVELOPMENT HowTo guides for details about how to run test locally. Artifacts// Erlang/OTP Github Action Bot |
f1e3840
to
7f9c349
Compare
d5008c9
to
6eb9932
Compare
66d874c
to
6015499
Compare
26e5986
to
05ea2d2
Compare
This middlebox mode is partially negotiated: If the client provides a non empty session ID the "compatibility middle box mode" should be used. Closes erlang#6241
05ea2d2
to
b7e1bf0
Compare
@IngelaAndin We are using Rabbit 3.11.27 and Erlang OTP 25.3.2.7 and still seeing this errors in our RMQ logs
|
@GitJadhav I have no reason to believe that OTP-25.3.2.7 is not handling middlebox compatibility mode correctly, we also You are not providing enough context for me to help you. I guess you are only asking about the last line in the log. What might help is if you know what client that is connecting when this happens. If you could connect with this client and set the server log_level to debug that could help. |
Closes #6241