On 12/26/08 8:12 PM, "Victor Duchovni"
wrote:
> Note, some CAs ignore SAN entires in the CSR and either don't support
> SAN certs at all, or require a separate SAN form to be filled in when
> uploading the CSR.
i can confirm that go daddy respects the san in their 5-domain cert product.
__
On Fri, Dec 26, 2008 at 07:25:00PM -0500, Tom Worster wrote:
> On 12/26/08 4:45 AM, "Kyle Hamilton" wrote:
>
> > To deal with this, you need to either put the two domains on separate
> > ports (which causes URLs of the form https://www.example2.com:4433/ ),
> > or create a certificate with the s
On 12/26/08 4:45 AM, "Kyle Hamilton" wrote:
> To deal with this, you need to either put the two domains on separate
> ports (which causes URLs of the form https://www.example2.com:4433/ ),
> or create a certificate with the subjectAlternativeName extension.
> The sAN is a list of values of the fo
i would recommend making 2 domains with the same extension and then
use a wildcard certificate.
for a quick test you can use the DOS batch script i made at my latest
blog post ( http://codingathome.blogspot.com ) and make a cert with
the CNAME of *.example.com . then you can run 2 virtual apac
Unless you're dealing with a new version of Apache which can handle
Server Name Indication (a relatively recent TLS extension), you cannot
have multiple certificates on the same IP:port combination. (It's a
"chicken and egg" problem: the HTTP Host: header is what contains the
data about what hostn
