www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Morley <ad...@islandhosting.com>
Subject general/7280: RemoveHandler "leak"
Date Mon, 19 Feb 2001 21:45:35 GMT

>Number:         7280
>Category:       general
>Synopsis:       RemoveHandler "leak"
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Mon Feb 19 13:50:00 PST 2001
>Originator:     admin@islandhosting.com
>Release:        1.3.14
FreeBSD 4.0, GCC, Pentium
One of our customers was using RemoveHandler in an .htaccess file to turn off SSI for certain
file extensions (eg: RemoveHandler .shtml)

When Apache first fires up everything is fine.  SSI is disabled for his pages and his pages
only.  But after his pages have been hit for a while, this setting begins to affect other
pages on the server.  It's as if the child process disables the handler but doesn't reinstate
it after the pages are served, so the next request that comes in also has SSI disabled.  Eventually
SSI is disabled on every child process.  Restarting the server "fixes" it.


 [In order for any reply to be added to the PR database, you need]
 [to include <apbugs@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database 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!     ]

View raw message