DUT MUST handle "chunked" response with bad Content-Length header sent to an HTTP/1.0 client
This test case tests the following 3 requirement(s).
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.
More information related to this test case may be available in the corresponding test clause documentation.
This test case belongs to the following 1 groups:
This test case identifier is test_case/rfc2616/chunked-1p0-badClen-toClt. Please use that identifier when refering to this test case.
|© The Measurement Factory||Co-Advisor · head-mid58||terms · privacy|