Why this is a matter to the Apache? In a real scenario, consider that an Apache Reverse Proxy servicing to 100 web servers, one of these servers is turned off or...Apache must service to other servers!! I turned off a server to solve this conflict. Why Apache never read another Virtual Host configuration?
On Wednesday, March 17, 2021, 07:45:47 PM GMT+3:30, Eric Covener <cove...@gmail.com> wrote: On Wed, Mar 17, 2021 at 12:05 PM Jason Long <hack3r...@yahoo.com.invalid> wrote: > > Thank you. > My VM uses port forwarding. When I browse 127.0.0.1:2080 on my host then it > forwarded to my guest port 80. > > > Are you suggesting that a request which *would* go to 192.168.1.4 if it were > turned on, should in fact go to 192.168.1.20 if 192.168.1.4 is turned off? > > Yes. My browser can't distinguish my requests and when a server is off then > it must forwarded to other servers automatically. I know in a real scenario, > it solved by domain name. > If my configuration is OK, then Apache accepts a request from port 80, one of > my servers is turned off and Apache must forward it to another server. I used > " <VirtualHost *:80>" and not any IP. The configuration doesn't express this at all. Your configuration expresses one domain forwarded to one backend and a second domain forwarded to a second backend. I don't think what you describe is possible (there may be some obscure config to resemble it) or useful. No user has this expectation for a URL they're accessing. A service is either clustered behind a reverse proxy or it isn't. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
