A questions for the knowledgable SSL people here:
I experimented with setting socket timeouts to 1 second during HTTP/2's
keepalive reading and closing the connection after n such TIMEUP returns. That
works nicely on cleartext connections, but https:// return APR_EOF on reads
after the
On Tue, Jan 19, 2016 at 4:52 PM, Stefan Eissing
wrote:
>
> I experimented with setting socket timeouts to 1 second during
> HTTP/2's keepalive reading and closing the connection after n such
> TIMEUP returns. That works nicely on cleartext connections, but
> https:// return AP
Thanks, Yann! First tests show that that change does not help, though. Will
experiment with tweaking ssl_engine_io some...
> Am 20.01.2016 um 21:50 schrieb Yann Ylavic :
>
> On Tue, Jan 19, 2016 at 4:52 PM, Stefan Eissing
> wrote:
>>
>> I experimented with setting soc
Unexpected errors discard the brigade */
> Am 20.01.2016 um 21:50 schrieb Yann Ylavic :
>
> On Tue, Jan 19, 2016 at 4:52 PM, Stefan Eissing
> wrote:
>>
>> I experimented with setting socket timeouts to 1 second during
>> HTTP/2's keepalive reading and closing th
On Thu, Jan 21, 2016 at 11:52 AM, Stefan Eissing
wrote:
> However seems to do it. Anyone for/against applying it?
Looks good to me, APR_TIMEUP is recoverable after all (other httpd
callsites would fail as usual).
This will raise an INFO log line per timeup though (useful in the
failing case still
r 2016 11:52
> An: dev@httpd.apache.org
> Betreff: Re: socket timeouts
>
> However seems to do it. Anyone for/against applying it?
>
> ===
> --- modules/ssl/ssl_engine_io.c (revision 1725894)
> +++ module
investigate deeper on my own. Maybe needless fears on my
> side.
>
> Regards
>
> Rüdiger
>
>> -Ursprüngliche Nachricht-
>> Von: Stefan Eissing [mailto:stefan.eiss...@greenbytes.de]
>> Gesendet: Donnerstag, 21. Januar 2016 11:52
>> An: dev@htt
> -Ursprüngliche Nachricht-
> Von: Stefan Eissing [mailto:stefan.eiss...@greenbytes.de]
> Gesendet: Donnerstag, 21. Januar 2016 13:36
> An: dev@httpd.apache.org
> Betreff: Re: socket timeouts
>
> I think the patch handles that by checking that
> a) the call was d