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 P.
www.DNSbed.com
On Mon, 9 May 2011 14:18:09 +0800
Jeff P. [email protected] wrote:
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.
2011/5/9 Cedric J. [email protected]:
server_name xxx.example.com;
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 P.
www.DNSbed.com
Am 09.05.2011 09:06, schrieb Cedric J.:
server_name xxx.example.com;
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.
Hope this helps a bit,
Pascal
On Mon, May 09, 2011 at 09:06:27AM +0200, Cedric J. wrote:
server_name xxx.example.com;
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 S.
On Wed, 11 May 2011 14:06:16 +0400
Igor S. [email protected] wrote:
listen 443;
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:
Server names
Woops, indeed - sorry
(never used this syntax in my installation… )
On Mon, May 09, 2011 at 02:18:09PM +0800, Jeff P. wrote:
Thanks.
server should always have a name. Or it will be “” by default.
–
Igor S.