SPDY add_header with Alternate-Protocol

Richard Fussenegger richard at fussenegger.info
Thu Jan 15 17:11:46 UTC 2015

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).

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

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


On 1/15/2015 5:47 PM, Sergey Kandaurov wrote:
> On Jan 15, 2015, at 6:21 PM, Richard Fussenegger <richard at 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.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4237 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mailman.nginx.org/pipermail/nginx-devel/attachments/20150115/62cae75d/attachment.bin>

More information about the nginx-devel mailing list