Bug 42216 - RFE -- external overload procedure
Summary: RFE -- external overload procedure
Status: RESOLVED LATER
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mpm_worker (show other bugs)
Version: 2.2.4
Hardware: All All
: P5 enhancement (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords: MassUpdate
Depends on:
Blocks:
 
Reported: 2007-04-24 03:55 UTC by Juerg Umhang
Modified: 2018-11-07 21:09 UTC (History)
0 users



Attachments
implements OverLoadProcedure in worker.c (2.77 KB, patch)
2007-04-24 03:58 UTC, Juerg Umhang
Details | Diff
implements OverLoadProcedure in prefork.c (2.78 KB, patch)
2007-04-24 03:59 UTC, Juerg Umhang
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Juerg Umhang 2007-04-24 03:55:39 UTC
please consider this posting as a request for enhancement

httpd knows about his overload situation.
---- [error] server reached MaxClients setting, consider raising the MaxClients
setting
this overload is easily created by an external attacker. in case of an attack
you have to react. best done on a lower osi-layer (iptables, pf, ...).
realtime log analysis has his own odds and twists. we would prefer a call to an
'external helper procedure'.

additional tool to fight against DoS and even DDoS attacks.

patches for worker and prefork are available
Comment 1 Juerg Umhang 2007-04-24 03:58:29 UTC
Created attachment 20026 [details]
implements OverLoadProcedure in worker.c
Comment 2 Juerg Umhang 2007-04-24 03:59:21 UTC
Created attachment 20027 [details]
implements OverLoadProcedure in prefork.c
Comment 3 William A. Rowe Jr. 2018-11-07 21:09:52 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.