Bug 57756 - Config options for handling of pipelined request
Summary: Config options for handling of pipelined request
Status: NEW
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: Core (show other bugs)
Version: 2.5-HEAD
Hardware: All All
: P2 enhancement (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Depends on:
Reported: 2015-03-25 12:13 UTC by gmoniker
Modified: 2015-03-25 12:13 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description gmoniker 2015-03-25 12:13:12 UTC
Can a server config option be added to control MAX_REQUESTS_IN_PIPELINE in Apache 2.4+?

The handling of Pipelined request where a client request may live on for MAX_REQUESTS_IN_PIPELINE requests causes problems with modules that have not been sufficiently updated for Apache 2.4 even if they are in Linux distributions considered stable that also offer Apache 2.4 per default. See https://bugs.php.net/bug.php?id=68486 for example.

For server administrators this puts them between a rock and a hard place. On the one hand they have a developer audience demanding newer module versions, and on the other hand they don't have the resources to build stable distributions themselves, and they have a very limited option available in the Apache configuration to fallback to reliable behaviour. The aforementioned bug has been observed to completely lockup a webserver for module requests without anyone even maliciously trying to crash it.

The only option now would be to completely turn off keep-alive. If there is a option to set MAX_REQUESTS_IN_PIPELINE on/off or to a certain integer, this would be much preferable.