Mention encrypted listeners in protocol-listener API reference #2335
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The protocol-listener health check accepts protocol names with 's' for the encrypted listeners like
amqpsandmqtts. The health check distinguishes between encrypted and non-encrypted so to get a 200 when running AMQPS but not AMQP you need to query foramqps.This change mentions the encrypted protocol names. I've also combined
amqp091andamqp10asamqpwhich is what the health check translates these into.Also see https://github.com/rabbitmq/rabbitmq-server/blob/c7f6cad331443df0eaad668c2f1ca62410259c3a/deps/rabbitmq_management/src/rabbit_mgmt_wm_health_check_protocol_listener.erl#L71-L135. The health check normalizes the protocol names so it can accept quite a large range