Can Trace be disabled im looking through the source and not seeing a flag to
disable this?
Thanks
-MJ
On Thu, Jan 23, 2003 at 09:59:53AM -0500, Johnson, Michael wrote:
Can Trace be disabled im looking through the source and not seeing a flag to
disable this?
Let the over-reacting begin. :-P
(In case someone missed it, the whitepaper for what he's reacting to is
available at
* Johnson, Michael wrote:
Can Trace be disabled im looking through the source and not seeing a flag to
disable this?
per configuration - no.
But a trace request is mostly fulfilled, if there comes *any* answer. So
what should happen? Close the connection? Not very polite ;-)
nd
--
my @japh
: Re: RFC TRACE
On Thu, Jan 23, 2003 at 09:59:53AM -0500, Johnson, Michael wrote:
Can Trace be disabled im looking through the source and not
seeing a flag to
disable this?
Let the over-reacting begin. :-P
(In case someone missed it, the whitepaper for what he's
reacting
I would guess some error message should be displayed. Forbidden/ Method not
allowed?
-Original Message-
From: André Malo [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 23, 2003 10:18 AM
To: [EMAIL PROTECTED]
Subject: Re: RFC TRACE
* Johnson, Michael wrote:
Can Trace
* Johnson, Michael wrote:
I would guess some error message should be displayed. Forbidden/ Method not
allowed?
By the nature of TRACE I don't see that it would make much sense for an
origin server.
For a (mod_)proxy a 405 may be useful for security reasons.
YMMV.
nd
--
my @japh =
, 2003 10:42 AM
To: [EMAIL PROTECTED]
Subject: Re: RFC TRACE
* Johnson, Michael wrote:
I would guess some error message should be displayed.
Forbidden/ Method not
allowed?
By the nature of TRACE I don't see that it would make much
sense for an
origin server.
For a (mod_)proxy a 405
