zhicheng wang wrote:
hi, my colleague has find the solution is here: http://archives.real-time.com/pipermail/tomcat-users/2003-June/115025.html
Just for the record: it is at least questionable (from the rfc's point of view) to have your server respond to a TRACE with a 3xx and especially a 302 status code. A 302 indicated that the requested resource is available, but (temporarly) resides under a different URI which the server should return in the Location field of it's response. What the server should do in your case is respond with a 405 "Method not Allowed", indicating that regardless wether the resource is available or not, it may not be accessed with the HTTP method the client used.
I don't want to appread nitpicking, it's just that it is often my job to work around ill-behaving servers :-/
For what it's worth,
Phil
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
