httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 37043] - mod_rewrite causing Apache child looping
Date Wed, 12 Oct 2005 20:35:34 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=37043>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=37043





------- Additional Comments From rpluem@apache.org  2005-10-12 22:35 -------
If you cannot prevent users from doing such things with

AllowOverride none

(which will also boost performance, even more as rewriterules in .htaccess files
are known to be inefficient) or at least prevent users to override FileInfo
commands which would deny rewriterules in .htaccess files, then I fear you have
only organizational matters to fix this by
- identifying these users
- warn them
- lock them out if they do not behave well
It should be sufficient to kill the process with a SIGTERM (kill). SIGKILL (kill
-9) does not seem to be needed and should only be tried if a simple kill does
not work. As you are running the prefork MPM no other connections will be harmed
by this in contrast to the worker MPM.
To get back to the original case of your problem: Replacing

(.+)*

with

(.*)

should fix your problem and deliver the same results in terms of matching and
grouping.
The question is if ulimit -t makes sense because it limits not the actual usage
of the CPU but the total number of seconds a process can consume the CPU during
its lifetime. I am not quite sure what happens to the httpd child processes once
this time is used up. I fear this would have even more disturbing consequences
to your server as this could possibly hit other processes that do not misbehave,
but simply consumed the amount of CPU during their lifetime. Of course you can
use MaxRequestsPerChild to reduce this risk.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message