Bug#492130: apache2.2-common: HTTP Trace enabled in default configuration

To: Thom May <thom@clearairturbulence.org>
Cc: 492130@bugs.debian.org
Subject: Bug#492130: apache2.2-common: HTTP Trace enabled in default configuration
From: Dario Griffo <dariogriffo@gmail.com>
Date: Thu, 24 Jul 2008 09:35:30 -0300
Message-id: <[🔎] 48887712.9080705@gmail.com>
Reply-to: Dario Griffo <dariogriffo@gmail.com>, 492130@bugs.debian.org
In-reply-to: <[🔎] 8a5e1dd40807240459w23cc6527neca9d158a5a0184@mail.gmail.com>
References: <[🔎] 20080723214431.360.57738.reportbug@illusion.eisenheim.com.ar> <[🔎] 8a5e1dd40807240459w23cc6527neca9d158a5a0184@mail.gmail.com>

Thom May wrote:

no, since that would imply having mod_rewrite enabled out of the box.
http://www.apacheweek.com/issues/03-01-24#news


What if using TraceEnable directive?
http://httpd.apache.org/docs/2.0/mod/core.html#traceenable

I'm testing it in my server wich i've installed few days ago, just totry some stuff, didn't enabled anithing else, but this directive andTRACE request are disallowed.

Reply to:

References:
- Bug#492130: apache2.2-common: HTTP Trace enabled in default configuration
  - From: Dario Griffo <dariogriffo@gmail.com>
- Bug#492130: apache2.2-common: HTTP Trace enabled in default configuration
  - From: "Thom May" <thom@clearairturbulence.org>

Prev by Date: Bug#492130: apache2.2-common: HTTP Trace enabled in default configuration
Next by Date: Bug#492295: apr_1.3.2-1(mips/experimental): FTBFS: test failure
Previous by thread: Bug#492130: apache2.2-common: HTTP Trace enabled in default configuration
Next by thread: Bug#492295: apr_1.3.2-1(mips/experimental): FTBFS: test failure
Index(es):
- Date
- Thread