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 addi
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 SP
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
On Jan 15, 2015, at 6:21 PM, Richard Fussenegger
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
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.
For example seen at:
https://github.c
