I am in the process of migrating from one domain to another, each of which has a SSL certificate, but I'm having difficulty getting both to work (i.e. if the user comes into https://a.com/, I am redirecting them to https://b.com/, which means the certs for a.com and b.com both have to be presented to the client).
If I do this (non-essential elements stripped):
Binding {
Port = 443
Interface = ::
}
UrlToolkit {
ToolkitID = a
Match (.*) Redirect //b.com$1
}
VirtualHost {
Hostname = a.com
SSLcertFile = a.com.pem
UseToolkit = a
}
VirtualHost {
Hostname = b.com
SSLcertFile = b.com.pem
}
it will not work. However, if I move a.com's SSLcertFile into the binding, like so:
Binding {
Port = 443
Interface = ::
SSLcertFile = a.com.pem
}
UrlToolkit {
ToolkitID = a
Match (.*) Redirect //b.com$1
}
VirtualHost {
Hostname = a.com
UseToolkit = a
}
VirtualHost {
Hostname = b.com
SSLcertFile = b.com.pem
}
it works, which doesn't seem to match the documentation (i.e. it should never fall back to the SSLcertFile in the binding, because a virtual host _is_ defined for the domain).
Any clues as to why the 'proper' configuration doesn't work?
Rodney