Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (nike.apache.org: domain of gstein@gmail.com designates
 209.85.220.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4F6A3304.6070802@catseye.org>
References: 
 <CALK=YjO0q0ky==5dNfjRf6LYZ+P4EvLtGtfVQbj50i8BmxoPQQ@mail.gmail.com>
	<DF258780-D8E7-4F4A-A244-2F932A70DCE0@gbiv.com>
	<201203202004.31796.sf@sfritsch.de>
	<10EBFF04-E21C-4BE2-8373-9335CC4FAC4E@jaguNET.com>
	<74E8D133-C719-4DA9-8E3D-2F0D95D29AE5@gbiv.com>
	<4F6A3304.6070802@catseye.org>
Date: Wed, 21 Mar 2012 16:02:09 -0400
Message-ID: 
 <CABD8fLUvLM_3dbQQm6kV5c+Kgx5H79d65virnO=2NvPA1WSM7A@mail.gmail.com>
Subject: Re: TRACE still enabled by default
From: Greg Stein <gstein@gmail.com>
To: dev@httpd.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Wed, Mar 21, 2012 at 15:59, Mark Montague <mark@catseye.org> wrote:
> On March 21, 2012 15:33 , "Roy T. Fielding" <fielding@gbiv.com> wrote:
>>
>> TRACE won't work at all if the most popular end-point doesn't support it=
.
>
> Why would this be a bad thing? =A0Or, to phrase it another way, what are =
the
> situations in which it is desirable that TRACE be already-enabled on a we=
b
> server as opposed to having the owner of the web server enable the TRACE
> method in response to a specific debugging need?

Roy means that if we don't set the precedent for TRACE being present
and how it is supposed to work, then nobody else will. The Apache HTTP
server is effectively the embodiment and leader of the HTTP
specification.

Cheers,
-g