- From: Jamie Lokier <jamie@shareable.org>
- Date: Mon, 19 Apr 2010 13:36:05 +0100
- To: Mark Nottingham <mnot@mnot.net>
- Cc: Wenbo Zhu <wenboz@google.com>, ietf-http-wg@w3.org
Mark Nottingham wrote: > Well, it has to live with the consequences of sending that status line -- including the possibility that the request is malformed, incomplete, etc. Ah, but according to the spec, that should not be a consequence. If you send an "error status" an incomplete request is to be expected. The server shouldn't rely on getting the whole request. But if you send a non-error status, the spec doesn't suggest the client truncates the request - no more than normal anyway. So the server should be able to depend on getting the request just as much as if it hadn't sent the status yet (barring client implementation quirks). Are you saying the spec is incomplete in this regard? -- Jamie
Received on Monday, 19 April 2010 12:36:36 UTC