Hiho,
I'm currently testing a solution where an Apache webserver terminates SSL requests, forwards them to another Apache webserver which acts as a frontend for a Tomcat.
What's the goal?
Each customer has his own tomcat environment. They
must request their service via
PHP Code:
https://fix.public.domain/customerX
The reverse proxy terminates the request and sends plain http requests to the frontend Apache which
must follow the form
PHP Code:
http://customerX.internal.domain
The rest is handled by ajp. Well, it works but my current configuration has 2 disatvantages (maybe more but these annoying me
)
First I have to edit the configuration file on the reverse proxy each time I add a new environment/customer (...and I have to do it twice because I also must add the new one on the second Apache for the ajp connection). What I like is a kind of catch all customerX, Y, Z... requests and forward them to the frontend Apache where the correct decision is made. One solution could be a rewrite rule but is it really necessary or is there a smarter way?
Another disatvantage is that I have to add each internal domain to the internal DNS server so that the reverse proxy can resolve
PHP Code:
http://customerX, Y, Z.internal.domain
Well, this could be solved due a catch all entry (*.internal.domain) when no other entry matches but maybe there's another way.
Any suggestions or maybe other solutions?
OK
PS: reverse proxy and frontend should be based on Apache webserver. ngnix or other solutions are unscheduled at the moment.
