On 1/18/22 11:24 AM, Anatoly Laskaris wrote:
I'm sorry for not answering to the question directly, but why use apache2?
- Because Apache is already installed and listening on the port in
question.
- Because that's what the OP asked about.
- Because it might be IBM / Oracle HTTP Server which are re-rolls of
Apache HTTP Server.
- $REASONS
There are modern alternatives ...
Age of something doesn't mean a lot.
- TCP/IP is from the 80s and yet we are still using it.
- OSI is newer than IPv4.
- IPv6 is newer than IPv4 and OSI.
Yet we are still talking about the venerable IPv4.
And something completely different like Traefik
(https://doc.traefik.io/traefik/getting-started/quick-start/) which is
geared towards modern cloud native infrastructure with containers and
workload orchestrators like Nomad or Kubernetes.
Usually you don't configure Traefik with static config file, but with
metadata and annotations in K8S and Consul so it is dynamic and reactive.
I view adding /additional/ software / daemons as poor form, especially
when the /existing/ software can do the task at hand.
Don't overlook the port conflict.
Or you can use nginx (which is already considered pretty old and clunky,
but it is much easier than apache still).
Why start the email asking why something old is used and then finish the
email suggesting the possibility of using something else old?
--
Grant. . . .
unix || die
