Re: [gentoo-user] Reverse Proxy with Apache2

[Grant Taylor]

On 1/18/22 1:30 PM, Anatoly Laskaris wrote:
> Age migth mean a lot when we are talking about software. Modern software
> usually is easier to configure, has sane defaults, more secure and has
> integration with other modern software.

I'll concede that those points are /possibilities/.  But they are not 
guaranteed.

> And is much more popular in the community meaning better support.

I do not agree that something being more common means, much less 
implies, better support.  There are an awful lot of bad recommendations 
all over the Internet.

> I'm was not talking about adding software, I was talking about replacing
> software.

But you are.  Replacing something inherently implies adding and / or 
configuring something old with something new.

> Time saved in managing complex software that does a simple task can
> be applied elsewhere.

Sometimes yes, sometimes no.

> In regards to "already having a software" most modern applications don't
> require "having" them. It works out of the box, usually with one command
> and you can switch parts of your infrastructure without pain thanks to
> containers (or statically linked binaries in golang and rust) without
> downtime (if done right).

"if done right" is so over the top the /operative/ /phrase/ of that 
statement that it's not even remotely funny.

> Dynamic ports with service discovery == no port conflicts.

There's no dynamic ports / service discovery in what the OP asked about.

The OP asked how to configure a feature (reverse proxy) of the software 
that they are already (Apache HTTPD) using for a part of a URL 
(https://192.168.0.15:443/zv) for a service that's currently listening 
on a given IP and port pair (https://192.168.0.15:443/).

So please elaborate on what the right way is to replace (as in add new 
and remove old) the existing software /or/ split the IP & port 
(192.168.0.15 TCP port 443) across multiple daemons is.  I would very 
much be interested in learning how to do this the right way.

I can think of many ways to do this, but all of which require something 
intercepting the port & IP pair at some point up stream.

> Not that old as apache.

I take your statement to be that the Apache HTTPD developers and 
administrators have more experience than Nginx / caddy / traefik 
developers and administrators by the simple fact that it has existed longer.

What /new/ thing are you using to communicate with caddy / traefik if 
you don't use the old crufty IPv4 / IPv6?

> Nginx is still widly used (contrast to apache),

The first four reports I found when searching for web server popularity 
show that Apache and Nginx are the top two popular servers.  Which one 
is number one depends on the report.

Link -  Global Web Server Market Share January 2022
  - https://hostadvice.com/marketshare/server/

Link - Web and Application Servers Software Market Share
  - https://www.datanyze.com/market-share/web-and-application-servers--425

Link - Usage statistics of web servers
  - https://w3techs.com/technologies/overview/web_server

Link - January 2022 Web Server Survey
  - https://news.netcraft.com/archives/category/web-server-survey/

My opinion is that being the first, or the close second is a good 
indication that Apache is still wildly used.

> but is being replaced by caddy/traefik. Apache is ancient and I've
> never seen it running in production.

If you've never seen the first or second most popular web server running 
in production, I can only question where you are looking.

I know multiple people that have run Apache HTTP Server (both by Apache 
and rebranded by IBM / Oracle) web server in production on multiple 
platforms for each and every year for the last two decades.  I've 
personally run Apache in production for that entire time.



-- 
Grant. . . .
unix || die