spdy per location

[Richard Kearsley]

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: sajan at noppix.com
> o: (563) 726-0371
> c: (563) 447-0822
>
> Noppix LLC Logo
> 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.
>>
>> ----appa
>>
>>
>>
>> On Mon, Jul 8, 2013 at 3:06 PM, Richard Kearsley 
>> <rkearsley at blueyonder.co.uk <mailto:rkearsley at blueyonder.co.uk>> wrote:
>>
>>     Hi
>>     I'm trying to set up spdy so that I can choose weather or not to
>>     use it based on the server location that's accessed
>>     As I understand, the underlying protocol (http/https/spdy) is
>>     established first before any request can be sent (e.g. before we
>>     know which location it will match)
>>
>>     I know this example is totally impossible, but would like to know
>>     if there is a real way of doing it:
>>
>>     server
>>     {
>>         listen 80;
>>         listen 443 ssl spdy;
>>
>>         location /
>>         {
>>             spdy off;
>>             blah;
>>         }
>>
>>         location /spdy
>>         {
>>             spdy on;
>>             blah;
>>         }
>>     }
>>
>>     Many thanks
>>
>>     _______________________________________________
>>     nginx mailing list
>>     nginx at nginx.org <mailto:nginx at nginx.org>
>>     http://mailman.nginx.org/mailman/listinfo/nginx
>>
>>
>>
>>
>> _______________________________________________
>> nginx mailing list
>> nginx at nginx.org
>> http://mailman.nginx.org/mailman/listinfo/nginx
>
>
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20130709/f3a5c721/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 7312 bytes
Desc: not available
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20130709/f3a5c721/attachment.png>