The following reply was made to PR mod_proxy/3202; it has been noted by GNATS.
From: [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: mod_proxy/3202: High system utilization with v1.3.3 Date: Tue, 27 Oct 1998 14:47:34 -0800 Marc, I like your idea better. I was merely trying to fix the symptom. I am a system admin and part-time hack. Is there someone on the Apache team who will address this problem? Let me know if/how I can help. I'm not beyond looking at the code, just don't know if I'm qualified. Regards, Eric -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 27, 1998 10:35 AM To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: mod_proxy/3202: High system utilization with v1.3.3 [In order for any reply to be added to the PR database, ] [you need to include <[EMAIL PROTECTED]> in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ] [If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request ] [from a developer. ] [Reply only with text; DO NOT SEND ATTACHMENTS! ] Synopsis: High system utilization with v1.3.3 Comment-Added-By: marc Comment-Added-When: Tue Oct 27 10:34:40 PST 1998 Comment-Added: While it appears like your diagnosis of the problem is correct, the patch does make much sense to me. What it seems to be doing is simply not doing garbage collection based on if the response is cachable or not, when it should move the check for doing garbage collection into the parent and only fork if necessary.
