Ward off port confusion by maintaining a redirect
Bug #1643900 reported by
Peter Matulis
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
I understand that the apache redirect (80 to 5240) will eventually be removed. However, if HA is set up (haproxy) the port once again becomes 80. It would be better to keep the redirect idea but replace apache with a lighter weight mechanism (e.g. socat) which the admin can disable when they enable HA. HA status (i.e. implemented or not) should remain transparent to the end-user.
To post a comment you must log in.
Hi Peter,
I think we should fix HAProxy to not do port 80 then. Port 5240 should be used by default at all times, and we should be pointing users to that. if users want to use port 80 instead, we should provide means for them to configure it that way, but we should not be the ones pushing them to use it.
That said, there's plans to run MAAS alongside other services that bidn to port 80 and we dont want them to conflict.