Test Case: DUT MUST handle "chunked" response with a 16385Byte-long chunk-ext-val sent to an HTTP/1.1 client

22.783| starting test case test_case/rfc2616/chunked-1p1-longValExt-16385-toClt from test_clause/rfc2616/chunked-1p1 clause
22.783| server accepting HTTP queries at 172.16.0.1:8080
22.783| client connecting to 172.16.0.7:80; 3 attempt(s)
22.784| client at 172.16.0.1:1189 connected to 172.16.0.7:80
22.784| client will send 94 bytes (94 + 0)
GET http://172.16.0.1:8080/vidtlncuvmke HTTP/1.1\r\n
Host: 172.16.0.1:8080\r\n
Connection: close\r\n
\r\n

22.784| client at 172.16.0.1:1189 expects to write to 172.16.0.7:80
22.784| client at 172.16.0.1:1189 wrote 94 bytes
22.784| client at 172.16.0.1:1189 stops writing to 172.16.0.7:80
22.784| client at 172.16.0.1:1189 expects to read from 172.16.0.7:80
22.785| server at 172.16.0.1:8080 accepted connection from 172.16.0.7:1177
22.785| server at 172.16.0.1:8080 expects to read from 172.16.0.7:1177
22.785| server at 172.16.0.1:8080 read 116 bytes
22.785| server got request headers (116 bytes)
GET /vidtlncuvmke HTTP/1.1\r\n
Host: 172.16.0.1:8080\r\n
Max-Forwards: 10\r\n
Connection: close\r\n
Via: 1.1 172.16.0.1:8080\r\n
\r\n

22.785| expecting no message body
22.785| no message body data to parse
22.785| server expects no more request data (after 116 + 0 = 116 bytes)
22.785| server at 172.16.0.1:8080 stops reading from 172.16.0.7:1177
22.785| server at 172.16.0.1:8080 expects to write to 172.16.0.7:1177
22.786| server will send 16606 bytes
HTTP/1.1 200 OK\r\n
Transfer-Encoding: chunked\r\n
Date: Tue, 07 Jan 2003 17:32:17 GMT\r\n
Connection: close\r\n
\r\n
64; name=ousgoho[ ... 16362 bytes, MD5: 1aa6c7d8d278a14ee59c55d75e02b46d ]bqfevdwpdhhjgnva\r\n
ovkuwiktpbvmbpdehiifnhwrqgcwvaxjvjdtrpmirkvuzyyiiipwpmpisteptdyqpdjgsyrjimdjmdrumjsdxjlpdqewvepkjytb\r\n
0\r\n
\r\n

22.787| server at 172.16.0.1:8080 wrote 16606 bytes
22.787| server at 172.16.0.1:8080 stops writing to 172.16.0.7:1177
22.787| server stops servicing connection with 172.16.0.7:1177
22.787| server at 172.16.0.1:8080 closing connection to 172.16.0.7:1177
22.788| client at 172.16.0.1:1189 read 319 bytes
22.789| client parsed response headers (208 bytes)
HTTP/1.1 200 OK\r\n
Date: Tue, 07 Jan 2003 17:32:16 GMT\r\n
Server: Apache/2.1.0-dev (Unix)\r\n
Via: 1.1 172.16.0.1:8080\r\n
Connection: close\r\n
Transfer-Encoding: chunked\r\n
Content-Type: text/plain; charset=ISO-8859-1\r\n
\r\n

22.789| expecting chunked encoding to determine message body length
22.789| parsed 111 bytes of message body:
64\r\n
ctgyefyjibsntewkaokggxelwmxkrwqvsxtweuhovbdogaaiqnrwkxiijhsafjwxirvoldegejwmjzxamqyynigyrabxlzwvqsle\r\n
0\r\n
\r\n

22.789| client expects no more data (after 208 + 111 = 319 bytes)
22.789| fyi: successfully decoded chunked message body: 100-byte content + 0-byte trailer
22.789| content size: 100
22.789| client at 172.16.0.1:1189 stops reading from 172.16.0.7:80
22.789| client stops servicing connection with 172.16.0.7:80
22.789| client at 172.16.0.1:1189 closing connection to 172.16.0.7:80
22.790| server stops accepting HTTP queries at 172.16.0.1:8080
22.790| fyi: DUT preserved (did not decode) chunked transfer encoding
22.790| finished case: test_case/rfc2616/chunked-1p1-longValExt-16385-toClt
22.790| result code: violation
22.790| result reason: DUT modified content of a chunked message