Um, trying to look into my crystal ball here.
Web proxies in general cannot cache SSL connection content, must pass the traffic through unaltered, and cannot view the content as it passes through.
Is this bad for the following reasons?
- High traffic on your site because of lack of caching (may be able to alleviate with tuning cache settings, allowing browser to cache properly).
- High traffic on your web-proxy because of lack of caching ... buy a bigger pipe or proxy.
- Cannot see browser traffic for remote web sites that you don't control (might be porn, viruses, data exfiltration).
- One obnoxious workaround to this is to install your certificate in the PCs you control and decrypt and re-encrypt traffic at the gateway for your staff (man-in-the middling the connections between your staff and their remote websites).
Note that this is only a problem for simple configurations using a single IP address and a single Apache installation. Other configurations are:
- Proper virtual host (Xen, VirtualBox, Virtual PC, etc) with its own public IP address.
- Server with multiple IP's and One or Two Apache instances configured correctly.
- Reverse Proxy configuration with 2 External IP Addresses redirected to different HTTPS Daemons on a box running on different ports.
- There is an extension to HTTPS That allows for multiple SSL Certificates specifically for this use case, I dont know how well it is implemented in Servers, Proxies and Browsers.