----- Original Message -----
From: egc <[email protected]>
Date: Mon, 22 Nov 2010 16:54:44 -0500
Subject: [us...@httpd] interpreting Nessus scan results | TRACE & TRACK?
To: [email protected]
Greetings --
Running 2.2.17 on a CentOS 5.5 host. All the usual security tweaks
(or, at least the ones I'm familiar with) in place. Had our network
types run a Nessus scan against the host - all fine, except for the
following, which I'm having trouble interpreting (and hoping for some
'interpretative guidance' here). It suggests using a rewrite to handle
the issue (something I've never done). I'm also not entirely sure of
what TRACE and TRACK do?
Just set the TraceEnable directive to off. The rewrite rules only apply
for older versions of apache that did not support TraceEnable.
--
Justin Pasher
Distribion
http://support.distribion.com/
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: [email protected]
" from the digest: [email protected]
For additional commands, e-mail: [email protected]
