httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roy T. Fielding" <>
Subject Re: svn commit: r290519 - /httpd/httpd/trunk/CHANGES
Date Thu, 22 Sep 2005 11:31:42 GMT
The RFC 2616 says

    The presence of a message-body in a request is signaled by the
    inclusion of a Content-Length or Transfer-Encoding header field in
    the request's message-headers. A message-body MUST NOT be included in
    a request if the specification of the request method (section 5.1.1)
    does not allow sending an entity-body in requests. A server SHOULD
    read and forward a message-body on any request; if the request method
    does not include defined semantics for an entity-body, then the
    message-body SHOULD be ignored when handling the request.

so I have no clue what

> +  *) Added TraceEnable [on|off|extended] per-server directive to alter
> +     the behavior of the TRACE method.  This addresses a flaw in proxy
> +     conformance to RFC 2616 - previously the proxy server would 
> accept
> +     a TRACE request body although the RFC prohibited it.  The default
> +     remains 'TraceEnable on'.  [William Rowe]

claims to be saying.  The proxy server SHOULD accept and forward
the message body and SHOULD ignore it.  Which means the options should
be on|off|rejectbody if you want to configure such behavior.


View raw message