On 4/17/2014 3:46 PM, Yehuda Katz wrote:
On Thu, Apr 17, 2014 at 3:12 PM, Mark London <m...@psfc.mit.edu <mailto:m...@psfc.mit.edu>>wrote:So I've been trying to find a configuration that redirects HTTPS://XXX.COMto HTTPS://WWW.XXX.COM. Unfortunately, every configuration that I've tried, doesn't work. All of the rewrite and redirect rules, are applied after the browser checks the certificate against the URL. Thus, the warning web page always appears.This is the expected behavior and other than issuing a new certificate and using another vhost (with SNI - generally not compatible with Windows XP and some other devices) or reissuing the same certificate with an additional name, there is no way around this.
Thanks, that confirms what I thought. - Mark
