Welcome! Log In Create A New Profile

Advanced

Re: server_name for https

Pascal Nitsche
May 09, 2011 05:50AM
Am 09.05.2011 09:06, schrieb Cedric Jeanneret:
> On Mon, 9 May 2011 14:18:09 +0800
> Jeff Pang<jeffrpang@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
>
> Cheers,
>
> C.

Even this is not needed since nginx does support SNI.

http://en.wikipedia.org/wiki/Server_Name_Indication

Hope this helps a bit,

Pascal

_______________________________________________
nginx mailing list
nginx@nginx.org
http://nginx.org/mailman/listinfo/nginx
Subject Author Posted

server_name for https

Jeff Pang May 09, 2011 02:20AM

Re: server_name for https

Cedric Jeanneret May 09, 2011 03:08AM

Re: server_name for https

Jeff Pang May 09, 2011 03:40AM

Re: server_name for https

Pascal Nitsche May 09, 2011 05:50AM

Re: server_name for https

Igor Sysoev May 11, 2011 06:08AM

Re: server_name for https

Cedric Jeanneret May 11, 2011 06:18AM

Re: server_name for https

Igor Sysoev May 11, 2011 06:08AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 184
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready