On 4 February 2013 14:20, Harold Pritchett wrote:
> On 2/3/2013 11:47 PM, Bent Terp wrote:
> > So my advice is to use a wildcard domain covering *.mycompany.com - but
> remember that mycompany.com does not match *.mycompany.com, so you'll
> need a redirect to
> > www.mycompany.com BR Bent PS
On 2/3/2013 11:47 PM, Bent Terp wrote:
> So my advice is to use a wildcard domain covering *.mycompany.com - but
> remember that mycompany.com does not match *.mycompany.com, so you'll need a
> redirect to
> www.mycompany.com BR Bent PS Just realised that we did this on nginx not
> apache,
> > Serving multiple ssl certificates requires SNI on server and also
> > client support.
> >
> >
http://www.rackspace.com/knowledge_center/article/serving-secure-sites-with-sni-on-apache
>
> this works on Centos 6 without messing up openssl libraries :)
Take a look at this freeIPA how to I wrote
On Mon, Feb 4, 2013 at 5:02 AM, Harold Pritchett wrote:
> I know that the upstream provider often provides services added to new
> releases as updates to the current release. My question is how can I get
> multiple secure web sites on a
> single IP address and port? Has the upstream provider ad
4 matches
Mail list logo
