You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@httpd.apache.org by Stefan Eissing <st...@greenbytes.de> on 2021/06/29 13:16:59 UTC

ssl coalescing filter too aggressive?

Could someone with understanding of the mod_ssl output filters have a look at: https://bz.apache.org/bugzilla/show_bug.cgi?id=65402

It looks as if HTTP/2 frames are buffered. The browser sees a TimeToFirstByte of 12 seconds, but the server logs show that the frame data was put into the connection output filters shortly after the request started - accompanied by a FLUSH buckets.

Thanks, Stefan

Re: ssl coalescing filter too aggressive?

Posted by Ruediger Pluem <rp...@apache.org>.


On 6/29/21 3:16 PM, Stefan Eissing wrote:
> Could someone with understanding of the mod_ssl output filters have a look at: https://bz.apache.org/bugzilla/show_bug.cgi?id=65402
> 
> It looks as if HTTP/2 frames are buffered. The browser sees a TimeToFirstByte of 12 seconds, but the server logs show that the frame data was put into the connection output filters shortly after the request started - accompanied by a FLUSH buckets.

Hm, from memory and a quick look at ssl_io_filter_coalesce flush buckets should cause the coalesce filter to pass down everything
down the filter chain.

Regards

Rüdiger