Rabbit and Flower sites http without https option?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 176
- Forks
- 74
- Avg merge
- 5d 3h
- Merged PRs (30d)
- 21
Description
Hi,
It looks like the Rabbit and Flower admin consoles are hardcoded to use http and are not setup to use https. What do you recommend to change this so we can use https properly on these?
Would this require setting up a reverse proxy with caddy
e.g.
{$DOMAIN_NAME}/rabbitmq/* {
reverse_proxy rabbit:{$RABBITMQ_MANAGEMENT_PORT}
}
{$DOMAIN_NAME}/flower/* {
reverse_proxy flower:{$FLOWER_PUBLIC_PORT}
}
and updating the hard coded URLs in context_processors.py to:
'RABBITMQ_MANAGEMENT_URL': f"https://{settings.DOMAIN_NAME}/rabbitmq",
'FLOWER_URL': f"https://{settings.DOMAIN_NAME}/flower",
Or is there another route?
What other security measures are you taking to secure the various admin consoles?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing context_processors.py and the deployment configuration for the RabbitMQ and Flower admin consoles. Compare the hardcoded URLs with the proposed reverse-proxy routes, then determine the project's supported HTTPS and access-control approach. Done should mean the consoles are reachable securely through the configured domain without breaking their existing links.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rabbitmq
- Domain
- backend, devops, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100