Welcome! Log In Create A New Profile

Advanced

Re: spdy per location

All files from this thread

File Name File Size   Posted by Date  
NewNoppixEmailLogo.png 7.1 KB open | download Sajan Parikh 07/08/2013 Read message
smime.p7s 4.4 KB open | download Sajan Parikh 07/08/2013 Read message
7.1 KB open | download dbradfield 07/09/2013 Read message
July 09, 2013 12:52PM
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@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@blueyonder.co.uk <mailto:rkearsley@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@nginx.org <mailto: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

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Attachments:
open | download - (7.1 KB)
Subject Author Posted

spdy per location

dbradfield July 08, 2013 09:08AM

Re: spdy per location

António P. P. Almeida July 08, 2013 10:46AM

Re: spdy per location Attachments

Sajan Parikh July 08, 2013 12:42PM

Re: spdy per location Attachments

dbradfield July 09, 2013 12:52PM

Re: spdy per location

Sylvia July 08, 2013 10:49AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 173
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 500 on July 15, 2024
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready