Re: SPDY add_header with Alternate-Protocol

[Richard Fussenegger]

But isn't nginx advertising them without manual adding of such headers? I mean, why configure SPDY on the listen directive when it isn't going to be used by clients (which is not the case, all browsers happily connect via SPDY).

add_header Alt-Svc h2=":666"; # I love id software's reserved port.

Richard

On 1/15/2015 5:47 PM, Sergey Kandaurov wrote:

I fully understand that I could run an HTTP/2 server listening on a different port and configure nginx to advertise this.

On Jan 15, 2015, at 6:21 PM, Richard Fussenegger <rich...@fussenegger.info> 
wrote:

I'm often seeing the advice to add the following line to your SPDY 
configuration:

add_header Alternate-Protocol  443:npn-spdy/3;

Is this actually necessary? I mean, my Firefox is connecting via SPDY to my 
nginx and I don’t have this in my configuration.

The Alternate-Protocol header is used for advertising such capability,
It is mentioned in SPDY/2 draft, and later removed.

draft-ietf-httpbis-alt-svc was influenced by its design for the Alt-Svc header.

smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
nginx-devel mailing list
nginx-devel@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-devel