the constant value here is optimal for most cases, like another patch that
optimizing ssl initial write buffer size for large certificate, I think having
a knob at conf file did not make any difference.
On 2015-05-13 12:57 , SplitIce Wrote:
Good Job.
Perhaps rather than changing the cons
Good Job.
Perhaps rather than changing the constants, they could be exposed as
configuration options?
On Wed, May 13, 2015 at 12:28 PM, chen wrote:
> 1) we will have that fixed
> 2) no api is exposed by openssl that we can use to trigger a FLUSH, use
> SSL_write is what we can do. If we inspect
1) we will have that fixed
2) no api is exposed by openssl that we can use to trigger a FLUSH, use
SSL_write is what we can do. If we inspect the data using wireshark, you will
find out that one SSL_write we result in one ssl record.
3) there are some old linux box that are still using IW4,
To
Awesome, thanks for putting this together!
On Tue, May 5, 2015 at 6:39 AM, chen wrote:
> There are 3 conditions, if true at the same time, may trigger SSL_write to
> send small record over the link, hard coded 1400 bytes at this time to
keep
> it fit into MTU size. We just send out 3 of this sma
I'm trying to debug a SPDY 3.1 protocol error that you get when
combining nginx, Chrome, and ngx_pagespeed.
Chrome sends a SPDY request for /pagespeed_static/1.JiBnMqyl6S.gif as:
:host = www.kluisstore.nl
:method = GET
:path = /pagespeed_static/1.JiBnMqyl6S.gif
:scheme = https
:version = HTTP/1.1
