February 14th, 2013, 02:14 PM
Understand ssl setup
- If the user support SNI and hit https://myurl1.server.com or https://myurl2.server.com it will match the right vhost. (the last 2 vhosts)
- If the user does not support SNI and hit https://myurl1.server.com or https://myurl2.server.com it will be catch by the fallback vhost (the first on port 443). It contains the SAN certificate and it will hit the server again to do the match. This time it will hit the last 2 vhost.
- If the user enter an unknown url with either http or https it will be catch in the first vhost that show a error page.
I have tested all 3 goals and it's working fine.
- When the user is hitting the SAN vhost (https) which make a new request to it self. How does Apache know it will match the last 2 vhost (443) when the proxypass in SAN vhost is using http(80)
- When the user is hitting the SAN vhost I can't see any requests in the SAN access log. The requests only appears in the last 2 vhost even if it goes through the SAN vhost. However I can see some bot requests in the SAN access log.
The code only contains the important parts.
show error page
ProxyPass / http://my-local-url-server/
ProxyPassReverse / http://my-local-url-server/
ProxyPass / http://mybackend1/
ProxyPassReverse / http://mybackend1/
ProxyPass / http://mybackend2/
ProxyPassReverse / http://mybackend2/