Hi,

I’m a bit puzzled about Apache’s behavior I recently explored on Debian,
the Apache version I run is v2.4.10-10, the latest.

I have multiple apache virtual namehosts configured on a single backend
server, respectively named as serverA.local and serverB.local, then I have
Apache reverse proxy configured to proxy these 2 namehosts also under 2
virtual names hosts on proxy as below:

<VirtualHost *:443>
  Servername serverA.com
  ProxyRequests Off
  ProxyPreserveHost On
  ProxyPass / https://serverA.local
  ProxyPassReverse / https://serverA.local/

  SSLEngine on
  ………
</VirtualHost>

<VirtualHost *:443>
  Servername serverB.com
  ProxyRequests Off
  ProxyPreserveHost On
  ProxyPass / https://serverB.local
  ProxyPassReverse / https://serverB.local/

  SSLEngine on
  ………
</VirtualHost>

the interesting thing I see is if I go to https://serverB.com, I see
https://serverA.com . But direct access to https://serverB.local and
https://serverA.com from the reverse proxy are completed fine. Somehow I
have a feeling that when Apache is proxying to the backend, it directs to
the "default server” on the backend, which in this serverA. Does anyone has
the same experience or did I miss anything that is simply?

Thanks.

Mizuki

Reply via email to