Thanks, this answers my actual question. In this case I never need it, since I only serve encrypted traffic to anyone.

Richard

On 1/15/2015 7:35 PM, Valentin V. Bartenev wrote:
On Thursday 15 January 2015 18:11:46 Richard Fussenegger wrote:
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).
[..]

They use SPDY because it's advertised during TLS handshake using
NPN/ALPN TLS extensions.

The "Alternate-Protocol" header was introduced for cases when no
other mechanisms available (e.g. for plain HTTP connections).

   wbr, Valentin V. Bartenev

_______________________________________________
nginx-devel mailing list
[email protected]
http://mailman.nginx.org/mailman/listinfo/nginx-devel


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
nginx-devel mailing list
[email protected]
http://mailman.nginx.org/mailman/listinfo/nginx-devel

Reply via email to