Bug 44619 - make http port configurable
make http port configurable
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: Apache
UCS 4.2
Other Linux
: P5 enhancement (vote)
: ---
Assigned To: UMC maintainers
UMC maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2017-05-17 10:37 CEST by Moritz Bunkus
Modified: 2020-07-03 20:55 CEST (History)
1 user (show)

See Also:
What kind of report is it?: Feature Request
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Moritz Bunkus 2017-05-17 10:37:33 CEST
It would be nice if the port number Apache listens on for unencrypted connections could be configured via config registry variables. Use cases include:

• running another daemon on port 80 as mentioned in [1]
• not having unencrypted connections available at all (which would be an extension of the existing mechanism `apache2/force_https`)

At the moment one has to modify existing templates in order to make Apache not listen on 80.

[1] https://help.univention.com/t/ucs-dienste-webinterface-auf-port-80-deaktivieren/5759
Comment 1 Ingo Steuwer univentionstaff 2020-07-03 20:55:18 CEST
This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.