TEST CASE INFO

Gist

DUT MUST handle "chunked" response with bad Content-Length header sent to an HTTP/1.0 client

Requirements

This test case tests the following 3 requirement(s).

1. "If a message is received with both a Transfer-Encoding header field and a Content-Length header field, the latter MUST be ignored" (rfc2616)
2. "in this case the server MUST delimit the message using methods defined in items 1,3 or 5 of this section" (rfc2616)
3. "If the message does include a non- identity transfer-coding, the Content-Length MUST be ignored" (rfc2616)

Developer notes

This case checks that a too-small Content-Length header field value is ignored. Checking that a too-large value is ignored would probably require pipelining and multiple server support. In this context, too-small and too-large is relative to the actual message-length, as determined by chunked encoding.

See also

More information related to this test case may be available in the corresponding test clause documentation.

Memberships

This test case belongs to the following 1 groups:

• server MUST NOT send transfer-codings to an HTTP/1.0 client (test_clause/rfc2616/chunked-1p0)

Internal Identifier

This test case identifier is test_case/rfc2616/chunked-1p0-badClen-toClt. Please use that identifier when refering to this test case.