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

Improper default for RabbitMQ Management API URL #1232

Open
skodde opened this issue Aug 12, 2022 · 0 comments
Open

Improper default for RabbitMQ Management API URL #1232

skodde opened this issue Aug 12, 2022 · 0 comments

Comments

@skodde
Copy link

skodde commented Aug 12, 2022

Hi,

It seems that from PR #896 (released with 0.9.4) broker_api (http_api) defaults to the same port of the broker (broker_url) inherited from Celery, in addition to the same user, address, etc., instead of continuing to hardcode the port as 15672.

if not http_api:
http_api = "http://{username}:{password}@{host}:{port}/api/{vhost}".format(
username=self.username, password=self.password,
host=self.host, port=self.port, vhost=self.vhost
)

vs.

if not http_api:
http_api = "http://{0}:{1}@{2}:15672/api/{3}".format(
self.username, self.password, self.host, self.vhost)

This seems counterproductive and appears to have broken several configurations in the wild.

RabbitMQ does not appear to support having the Management plugin listening on the same port as the AMQP listener, so there should not be a use case for this default.

On the other hand, using the same port as the default Management plugin listener (15672) would allow it to work without any additional Flower specific configuration, as it did in the past.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant