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.
--
Jeff Pang
www.DNSbed.com
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
Cheers,
C.
--
C?dric Jeanneret | System Administrator
021 619 10 32 | Camptocamp SA
cedric.jeanneret at camptocamp.com | PSE-A / EPFL
www.camptocamp.com | www.github.com/camptocamp
-------------- 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/20110509/975ca98c/attachment.pgp>
2011/5/9 Cedric Jeanneret <cedric.jeanneret at camptocamp.com>:
> 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
>
OK That's right thanks.
I have misunderstood the SSL Proxy maybe, now I got it.
--
Jeff Pang
www.DNSbed.com
Am 09.05.2011 09:06, schrieb Cedric Jeanneret:
> 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
>
> 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
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
--
Igor Sysoev
On Mon, May 09, 2011 at 02:18:09PM +0800, Jeff Pang 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.
server should always have a name. Or it will be "" by default.
--
Igor Sysoev
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>