httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karasulu, Alex" <>
Subject [users@httpd] [2.0] Better way to control TRACE and TRACK
Date Wed, 20 Jul 2005 12:53:50 GMT

In Apache 1.3 TraceEnable off was a valid option but it does not seem to
be carried into 2.0? 

The only option available is a rewrite which has to go into 100's of our
virtual host files and this means:

1. Allot of work  
2. Dealing with mod rewrite 

Here's what we do today to get around not having TraceEnable in 2.0:

        RewriteEngine on 
        ReWriteCond %{REQUEST_METHOD} ^(TRACE|TRACK) 
        ReWriteRule .* - [F] 

Also, we cannot just disable trace and/or track while compiling apache
2.0 or can we? 

Furthermore we can't use limit as it wont apply to TRACE.. 

   <LimitExcept GET POST PUT> 
        Deny from all 

Basically, is there a better way to do this reminiscent of the behavior
TraceEnable had in 1.3? 


The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message