https://bz.apache.org/bugzilla/show_bug.cgi?id=60244
--- Comment #6 from Laurence 'GreenReaper' Parry <greenrea...@hotmail.com> --- This behaviour should really be documented. It makes sense once you understand the reason, but is unexpected nevertheless, and has the potential for triggering hard-to-track bugs where it looks like the client may be at issue. Current browsers show the connections as "stalled" even though they may in fact have done their part in issuing the request. While HTTP/2 is not doing anything "wrong", per-se, it is a case where it breaks website workflows which worked fine with HTTP/1.1 on the same MPM. Possible locations to mention it: https://httpd.apache.org/docs/2.4/howto/http2.html https://httpd.apache.org/docs/2.4/mod/mod_http2.html#h2maxworkers ("If this directive is not used, mod_http2 will chose a value suitable for the mpm module loaded." is not enough, because it does not specify a value or the implications.) -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org For additional commands, e-mail: bugs-h...@httpd.apache.org
