server_name for https

[Cedric Jeanneret]

On Wed, 11 May 2011 14:06:16 +0400
Igor Sysoev <igor at sysoev.ru> wrote:

> On Mon, May 09, 2011 at 09:06:27AM +0200, Cedric Jeanneret wrote:
> > On Mon, 9 May 2011 14:18:09 +0800
> > Jeff Pang <jeffrpang at gmail.com> wrote:
> > 
> > > Hello,
> > > 
> > > Since HTTPS doesn't support vhost, shall we have the need to put the
> > > server_name command in the server section? for example,
> > > 
> > >          server {
> > >                 listen       443;
> > >                 server_name  xxx.example.com;
> > >                 ....
> > >          }
> > > 
> > > Thanks.
> > > 
> > > 
> > 
> > o_O since when does HTTPS not support vhosts ?
> > 
> > the only problem is when having multiple SSL vhosts on the same IP - the certificate has to cover all those vhosts.
> > 
> > To answer your question, you shall provide:
> > server_name $_;
> > 
> > it's the default vhost
> 
> This is not default virtual host. Please read this:
> http://nginx.org/en/docs/http/server_names.html#miscellaneous_names
> 
> 
Woops, indeed - sorry :/ (never used this syntax in my installation... )
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://nginx.org/pipermail/nginx/attachments/20110511/607871e6/attachment.pgp>