This issue is still relevant to me, and I do really think differently.
/manager is a default, not a standard. It works just fine in alternate locations. Although they should be secured in other ways, it is a good practice to relocate your administrative interfaces away from well-known paths.
Other solutions are possible but are not usable in all situations (like accessing a machine in a data center where only certain ports are visible from the outside.)
I also wonder why you consider this stale. I think of things as stale when a developer asks for more information and doesn't get it. A viable patch was proposed and not applied. Why not? Looking at it now, I'm thinking that maybe it needs to include code to migrate existing configuration so that the change will not break anything.
Please comment on what is needed to get this issue fixed.
Created an attachment (id=913)
Patch to remove /manager from tomcat deploy URL and update config field title