On 2/17/2011 4:41 AM, Mark Thomas wrote:
>
> I'm not particularly comfortable with this. I'm having a hard time
> coming up with a use case where some requests are swallowed and some are
> not. I think I'd prefer a per Connector or per Context attribute. I need
> to read the right part of the HTTP spec though since the wording there
> is likely to influence my views.
Of course, it's fun looking for "request message" in the spec, but if one
reads these literally, a response always follows the request line, headers
and message body as defined in those headers;
5 Request
A request message from a client to a server includes, within the
first line of that message, the method to be applied to the resource,
the identifier of the resource, and the protocol version in use.
Request = Request-Line ; Section 5.1
*(( general-header ; Section 4.5
| request-header ; Section 5.3
| entity-header ) CRLF) ; Section 7.1
CRLF
[ message-body ] ; Section 4.3
6 Response
After receiving and interpreting a request message, a server responds
with an HTTP response message.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
