Bug 51303 - TraceEnable 500 error
Summary: TraceEnable 500 error
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: Core (show other bugs)
Version: 2.0.64
Hardware: PC Linux
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Keywords: MassUpdate
Depends on:
Reported: 2011-05-31 18:37 UTC by Rob Mangiafico
Modified: 2018-11-07 21:09 UTC (History)
1 user (show)


Note You need to log in before you can comment on or make changes to this bug.
Description Rob Mangiafico 2011-05-31 18:37:30 UTC
With "TraceEnable Off" set in httpd.conf, and a GET or POST hit to a directory with a <Limit>" .htaccess file will randomly result in a 500 error with this in the error log:

[Tue May 31 13:54:28 2011] [alert] [client] /home/xyz/www/reviews/.htaccess: TRACE cannot be controlled by <Limit>, see TraceEnable

The actual GET line from the access-log:
--- - - [31/May/2011:13:54:28 -0400] "GET /reviews/summary.php/%238811 HTTP/1.0" 500 549 "-" "-" "-"

But this same GET went through fine a few minutes later:
--- - - [31/May/2011:14:06:54 -0400] "GET /reviews/summary.php/%238811 HTTP/1.0" 200 331 "-" "-" "-"

The .htaccess file is simply:
<IfModule mod_php4.c>
   php_value magic_quotes_gpc "Off"
   php_value magic_quotes_runtime "Off"
<Limit GET POST post>
order allow,deny
allow from all
deny from 64.41.142
deny from 64.41.168
deny from 64.14.3
deny from 216.35.7
deny from 209.67.114
deny from 165.193.42
deny from 216.49.80
deny from 64.41.140

We see this error periodically and randomly only on GETs/POSTs to php/cgi scripts in directories with <Limit> directives.
Comment 1 William A. Rowe Jr. 2018-11-07 21:09:44 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.