Thanks all
I think I will just open another port (looks like 6121 is registered
for spdy?)
because I'm not using hostnames (only IPs) and I don't like
redirects
so:
server
{
listen 80;
listen 443 ssl;
listen 6121 ssl spdy; # it will still fall-back to https if the
client doesn't support spdy
location /
{
blah;
}
}
Cheers
On 08/07/13 17:40, Sajan Parikh wrote:
I guess if you cover all your bases
when it comes to making sure your redirect where your users want
to go, this might be one use of 'www'. DOMAIN.COM can have SPDY
and WWW.DOMAIN.COM can have it
off.
Then you just redirect each location to the other one, or serve
it.
Sajan Parikh
Owner, Noppix LLC
e: sa...@noppix.com
o: (563) 726-0371
c: (563) 447-0822

On 07/08/2013 09:45 AM, António P. P. Almeida wrote:
spdy is a socket directive option. You cannot set
it outside of that context AFAICT.
What you can do is play with redirects between two
hosts, one with spdy and one without.
Since usually certs have at least one DNS name besides the
CN you can do it with the same cert. Probably
I haven't tested and don't know if Nginx complains about a
duplicated cert in different hosts.
It's not nice or clean. It's an ugly hack.
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
|
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx