/Test Case/: *cache MUST ignore max-age=8 in the name of blah=value extension response cache-directive* Subcase gist State Comment cache must treat cached entity as stale when the age exceeds max-age Cache-Control directive success cache did treat cached entity as stale when the age exceeds max-age Cache-Control directive ... directive success cache did treat cached entity as stale when the age exceeds max-age Cache-Control directive 89.401| starting test case test_case/rfc2616/ccExtension-max-age-name-toClt 89.401| Co-Advisor version: 2.1.4b 89.401| *step 1*: executing unaltered test case to make sure DUT supports the original cache-directive(s) /Subcase/: *cache must treat cached entity as stale when the age exceeds max-age Cache-Control directive* Subcase gist State Comment cache something success DUT proxied the transaction and possibly cached the response check that a given entity instance is cached and fresh success at the time of the request, entity instance appeared to be cached and fresh check that a given entity instance is not cached or cached but stale success at the time of the request, entity instance did not appear to be cached 89.401| starting sub-case test_case/rfc2616/ccRespDirMsg-max-age-obey 89.401| *step 1.1*: attempting to cache entity with max-age Cache-Control directive /Subcase/: *cache something* 89.401| starting sub-case test_case/rfc2616/cacheSmth 89.401| server accepting HTTP queries at 10.0.0.42:8081 89.402| client connecting to 10.0.0.42:8080; 3 attempt(s) 89.402| client at 10.0.0.42:62945 connected to 10.0.0.42:8080 89.402| client will send 92 bytes (92 + 0) GET http://10.0.0.42:8081/nqdppxiomndc HTTP/1.1\r\n Host: 10.0.0.42:8081\r\n Connection: close\r\n \r\n 89.402| client at 10.0.0.42:62945 expects to write to 10.0.0.42:8080 89.402| client at 10.0.0.42:62945 wrote 92 bytes to 10.0.0.42:8080 ( 92 bytes so far) 89.403| client at 10.0.0.42:62945 stops writing to 10.0.0.42:8080( after 92 bytes) 89.403| client at 10.0.0.42:62945 expects to read from 10.0.0.42:8080 89.403| server at 10.0.0.42:8081 accepted connection from 10.0.0.42:64233 89.403| server at 10.0.0.42:8081 expects to read from 10.0.0.42:64233 89.403| server at 10.0.0.42:8081 read 130 bytes from 10.0.0.42:64233 ( 130 bytes so far) 89.403| server got request headers (130 bytes) GET /nqdppxiomndc HTTP/1.1\r\n Host: 10.0.0.42:8081\r\n Max-Forwards: 10\r\n Connection: close\r\n Via: 1.1 10.0.0.42:8081 (Apache/2.0.54)\r\n \r\n 89.403| expecting no message body 89.404| expected message body format: opaque message body 89.404| no more message body data to parse 89.404| server expects no more request data (after 130 + 0 = 130 bytes) 89.404| server at 10.0.0.42:8081 stops reading from 10.0.0.42:64233( after 130 bytes) 89.405| server will send 205 bytes HTTP/1.1 200 OK\r\n Cache-Control: public\r\n Last-Modified: Thu, 03 Jun 2004 22:32:10 GMT\r\n Cache-Control: max-age=8\r\n Date: Fri, 03 Jun 2005 22:33:41 GMT\r\n Content-Length: 15\r\n Connection: close\r\n \r\n body-esffedulyd 89.405| server at 10.0.0.42:8081 expects to write to 10.0.0.42:64233 89.405| server at 10.0.0.42:8081 wrote 205 bytes to 10.0.0.42:64233 ( 205 bytes so far) 89.405| server at 10.0.0.42:8081 stops writing to 10.0.0.42:64233( after 205 bytes) 89.405| server stops servicing connection with 10.0.0.42:64233 89.405| server at 10.0.0.42:8081 closing connection to 10.0.0.42:64233 (read 130 bytes and wrote 205 bytes) 89.412| client at 10.0.0.42:62945 read 257 bytes from 10.0.0.42:8080 ( 257 bytes so far) 89.413| client parsed response headers (242 bytes) HTTP/1.1 200 OK\r\n Date: Fri, 03 Jun 2005 22:33:40 GMT\r\n Cache-Control: public, max-age=8\r\n Last-Modified: Thu, 03 Jun 2004 22:32:10 GMT\r\n Content-Length: 15\r\n Via: 1.1 10.0.0.42:8081 (Apache/2.0.54)\r\n Connection: close\r\n Content-Type: text/plain\r\n \r\n 89.413| expecting 15 bytes of message body based on Content-Length header 89.413| expected message body format: opaque message body 89.413| parsed 15 bytes of message body: body-esffedulyd 89.413| client expects no more data (after 242 + 15 = 257 bytes) 89.414| content size: 15 89.414| client at 10.0.0.42:62945 stops reading from 10.0.0.42:8080( after 257 bytes) 89.414| client stops servicing connection with 10.0.0.42:8080 89.414| client at 10.0.0.42:62945 closing connection to 10.0.0.42:8080 (read 257 bytes and wrote 92 bytes) 89.414| server stops accepting HTTP queries at 10.0.0.42:8081 89.414| finished case: test_case/rfc2616/cacheSmth 89.414| result code: success 89.414| result reason: DUT proxied the transaction and possibly cached the response 89.415| *step 1.2*: verifying whether the entity was cached and is fresh /Subcase/: *check that a given entity instance is cached and fresh* 89.415| starting sub-case test_case/rfc2616/checkCached-fresh 89.415| server accepting HTTP queries at 10.0.0.42:8081 89.415| client connecting to 10.0.0.42:8080; 3 attempt(s) 89.415| client at 10.0.0.42:61267 connected to 10.0.0.42:8080 89.415| client will send 92 bytes (92 + 0) GET http://10.0.0.42:8081/nqdppxiomndc HTTP/1.1\r\n Host: 10.0.0.42:8081\r\n Connection: close\r\n \r\n 89.416| client at 10.0.0.42:61267 expects to write to 10.0.0.42:8080 89.416| client at 10.0.0.42:61267 wrote 92 bytes to 10.0.0.42:8080 ( 92 bytes so far) 89.416| client at 10.0.0.42:61267 stops writing to 10.0.0.42:8080( after 92 bytes) 89.416| client at 10.0.0.42:61267 expects to read from 10.0.0.42:8080 89.416| client at 10.0.0.42:61267 read 265 bytes from 10.0.0.42:8080 ( 265 bytes so far) 89.417| client parsed response headers (250 bytes) HTTP/1.1 200 OK\r\n Date: Fri, 03 Jun 2005 22:33:40 GMT\r\n Content-Type: text/plain\r\n Last-Modified: Thu, 03 Jun 2004 22:32:10 GMT\r\n Cache-Control: public, max-age=8\r\n Content-Length: 15\r\n Via: 1.1 10.0.0.42:8081 (Apache/2.0.54)\r\n Age: 0\r\n Connection: close\r\n \r\n 89.417| expecting 15 bytes of message body based on Content-Length header 89.417| expected message body format: opaque message body 89.417| parsed 15 bytes of message body: body-esffedulyd 89.417| client expects no more data (after 250 + 15 = 265 bytes) 89.417| content size: 15 89.418| client at 10.0.0.42:61267 stops reading from 10.0.0.42:8080( after 265 bytes) 89.418| client stops servicing connection with 10.0.0.42:8080 89.418| client at 10.0.0.42:61267 closing connection to 10.0.0.42:8080 (read 265 bytes and wrote 92 bytes) 89.418| server stops accepting HTTP queries at 10.0.0.42:8081 89.418| finished case: test_case/rfc2616/checkCached-fresh 89.418| result code: success 89.418| result reason: at the time of the request, entity instance appeared to be cached and fresh 89.418| sleeping for 10 seconds to increase age of a cached entity 99.427| *step 1.3*: verifying whether the cached entity is still cached /Subcase/: *check that a given entity instance is not cached or cached but stale* 99.427| starting sub-case test_case/rfc2616/checkCached-notORstale 99.427| server accepting HTTP queries at 10.0.0.42:8081 99.428| client connecting to 10.0.0.42:8080; 3 attempt(s) 99.428| client at 10.0.0.42:49787 connected to 10.0.0.42:8080 99.428| client will send 92 bytes (92 + 0) GET http://10.0.0.42:8081/nqdppxiomndc HTTP/1.1\r\n Host: 10.0.0.42:8081\r\n Connection: close\r\n \r\n 99.428| client at 10.0.0.42:49787 expects to write to 10.0.0.42:8080 99.429| client at 10.0.0.42:49787 wrote 92 bytes to 10.0.0.42:8080 ( 92 bytes so far) 99.429| client at 10.0.0.42:49787 stops writing to 10.0.0.42:8080( after 92 bytes) 99.429| client at 10.0.0.42:49787 expects to read from 10.0.0.42:8080 99.429| server at 10.0.0.42:8081 accepted connection from 10.0.0.42:58312 99.429| server at 10.0.0.42:8081 expects to read from 10.0.0.42:58312 99.429| server at 10.0.0.42:8081 read 130 bytes from 10.0.0.42:58312 ( 130 bytes so far) 99.430| server got request headers (130 bytes) GET /nqdppxiomndc HTTP/1.1\r\n Host: 10.0.0.42:8081\r\n Max-Forwards: 10\r\n Connection: close\r\n Via: 1.1 10.0.0.42:8081 (Apache/2.0.54)\r\n \r\n 99.430| expecting no message body 99.430| expected message body format: opaque message body 99.430| no more message body data to parse 99.430| server expects no more request data (after 130 + 0 = 130 bytes) 99.430| server at 10.0.0.42:8081 stops reading from 10.0.0.42:58312( after 130 bytes) 99.431| server will send 205 bytes HTTP/1.1 200 OK\r\n Cache-Control: public\r\n Last-Modified: Thu, 03 Jun 2004 22:32:10 GMT\r\n Cache-Control: max-age=8\r\n Content-Length: 15\r\n Date: Fri, 03 Jun 2005 22:33:51 GMT\r\n Connection: close\r\n \r\n body-esffedulyd 99.431| server at 10.0.0.42:8081 expects to write to 10.0.0.42:58312 99.431| server at 10.0.0.42:8081 wrote 205 bytes to 10.0.0.42:58312 ( 205 bytes so far) 99.431| server at 10.0.0.42:8081 stops writing to 10.0.0.42:58312( after 205 bytes) 99.431| server stops servicing connection with 10.0.0.42:58312 99.431| server at 10.0.0.42:8081 closing connection to 10.0.0.42:58312 (read 130 bytes and wrote 205 bytes) 99.432| client at 10.0.0.42:49787 read 257 bytes from 10.0.0.42:8080 ( 257 bytes so far) 99.432| client parsed response headers (242 bytes) HTTP/1.1 200 OK\r\n Date: Fri, 03 Jun 2005 22:33:50 GMT\r\n Cache-Control: public, max-age=8\r\n Last-Modified: Thu, 03 Jun 2004 22:32:10 GMT\r\n Content-Length: 15\r\n Via: 1.1 10.0.0.42:8081 (Apache/2.0.54)\r\n Connection: close\r\n Content-Type: text/plain\r\n \r\n 99.433| expecting 15 bytes of message body based on Content-Length header 99.433| expected message body format: opaque message body 99.433| parsed 15 bytes of message body: body-esffedulyd 99.433| client expects no more data (after 242 + 15 = 257 bytes) 99.433| content size: 15 99.433| client at 10.0.0.42:49787 stops reading from 10.0.0.42:8080( after 257 bytes) 99.433| client stops servicing connection with 10.0.0.42:8080 99.433| client at 10.0.0.42:49787 closing connection to 10.0.0.42:8080 (read 257 bytes and wrote 92 bytes) 99.434| server stops accepting HTTP queries at 10.0.0.42:8081 99.434| finished case: test_case/rfc2616/checkCached-notORstale 99.434| result code: success 99.434| result reason: at the time of the request, entity instance did not appear to be cached 99.434| finished case: test_case/rfc2616/ccRespDirMsg-max-age-obey 99.434| result code: success 99.434| result reason: cache did treat cached entity as stale when the age exceeds max-age Cache-Control directive 99.434| *step 2*: repeating the same test case with the original cache-directive(s) replaced with max-age=8 in the name of blah=value extension response cache-directive; expecting a violation if the DUT correctly ignores those extensions /Subcase/: *cache must treat cached entity as stale when the age exceeds max-age Cache-Control directive* Subcase gist State Comment cache something success DUT proxied the transaction and possibly cached the response check that a given entity instance is cached and fresh success at the time of the request, entity instance appeared to be cached and fresh check that a given entity instance is not cached or cached but stale success at the time of the request, entity instance did not appear to be cached 99.434| starting sub-case test_case/rfc2616/ccRespDirMsg-max-age-obey 99.434| *step 2.1*: attempting to cache entity with max-age Cache-Control directive /Subcase/: *cache something* 99.435| starting sub-case test_case/rfc2616/cacheSmth 99.435| server accepting HTTP queries at 10.0.0.42:8081 99.435| client connecting to 10.0.0.42:8080; 3 attempt(s) 99.435| client at 10.0.0.42:52104 connected to 10.0.0.42:8080 99.435| client will send 92 bytes (92 + 0) GET http://10.0.0.42:8081/thnnunshkgzi HTTP/1.1\r\n Host: 10.0.0.42:8081\r\n Connection: close\r\n \r\n 99.436| client at 10.0.0.42:52104 expects to write to 10.0.0.42:8080 99.436| client at 10.0.0.42:52104 wrote 92 bytes to 10.0.0.42:8080 ( 92 bytes so far) 99.436| client at 10.0.0.42:52104 stops writing to 10.0.0.42:8080( after 92 bytes) 99.436| client at 10.0.0.42:52104 expects to read from 10.0.0.42:8080 99.436| server at 10.0.0.42:8081 accepted connection from 10.0.0.42:53394 99.436| server at 10.0.0.42:8081 expects to read from 10.0.0.42:53394 99.436| server at 10.0.0.42:8081 read 130 bytes from 10.0.0.42:53394 ( 130 bytes so far) 99.437| server got request headers (130 bytes) GET /thnnunshkgzi HTTP/1.1\r\n Host: 10.0.0.42:8081\r\n Max-Forwards: 10\r\n Connection: close\r\n Via: 1.1 10.0.0.42:8081 (Apache/2.0.54)\r\n \r\n 99.437| expecting no message body 99.437| expected message body format: opaque message body 99.437| no more message body data to parse 99.437| server expects no more request data (after 130 + 0 = 130 bytes) 99.437| server at 10.0.0.42:8081 stops reading from 10.0.0.42:53394( after 130 bytes) 99.438| server will send 224 bytes HTTP/1.1 200 OK\r\n Cache-Control: public\r\n Last-Modified: Thu, 03 Jun 2004 22:32:10 GMT\r\n Cache-Control: " max-age=8,max-age=8 "=blah\r\n Date: Fri, 03 Jun 2005 22:33:51 GMT\r\n Content-Length: 15\r\n Connection: close\r\n \r\n body-efpnzpbjgm 99.438| server at 10.0.0.42:8081 expects to write to 10.0.0.42:53394 99.439| server at 10.0.0.42:8081 wrote 224 bytes to 10.0.0.42:53394 ( 224 bytes so far) 99.440| server at 10.0.0.42:8081 stops writing to 10.0.0.42:53394( after 224 bytes) 99.440| server stops servicing connection with 10.0.0.42:53394 99.440| server at 10.0.0.42:8081 closing connection to 10.0.0.42:53394 (read 130 bytes and wrote 224 bytes) 99.440| client at 10.0.0.42:52104 read 276 bytes from 10.0.0.42:8080 ( 276 bytes so far) 99.441| client parsed response headers (261 bytes) HTTP/1.1 200 OK\r\n Date: Fri, 03 Jun 2005 22:33:50 GMT\r\n Cache-Control: public, " max-age=8,max-age=8 "=blah\r\n Last-Modified: Thu, 03 Jun 2004 22:32:10 GMT\r\n Content-Length: 15\r\n Via: 1.1 10.0.0.42:8081 (Apache/2.0.54)\r\n Connection: close\r\n Content-Type: text/plain\r\n \r\n 99.441| expecting 15 bytes of message body based on Content-Length header 99.441| expected message body format: opaque message body 99.441| parsed 15 bytes of message body: body-efpnzpbjgm 99.441| client expects no more data (after 261 + 15 = 276 bytes) 99.442| content size: 15 99.442| client at 10.0.0.42:52104 stops reading from 10.0.0.42:8080( after 276 bytes) 99.442| client stops servicing connection with 10.0.0.42:8080 99.442| client at 10.0.0.42:52104 closing connection to 10.0.0.42:8080 (read 276 bytes and wrote 92 bytes) 99.442| server stops accepting HTTP queries at 10.0.0.42:8081 99.442| finished case: test_case/rfc2616/cacheSmth 99.442| result code: success 99.442| result reason: DUT proxied the transaction and possibly cached the response 99.442| *step 2.2*: verifying whether the entity was cached and is fresh /Subcase/: *check that a given entity instance is cached and fresh* 99.443| starting sub-case test_case/rfc2616/checkCached-fresh 99.443| server accepting HTTP queries at 10.0.0.42:8081 99.443| client connecting to 10.0.0.42:8080; 3 attempt(s) 99.443| client at 10.0.0.42:52003 connected to 10.0.0.42:8080 99.443| client will send 92 bytes (92 + 0) GET http://10.0.0.42:8081/thnnunshkgzi HTTP/1.1\r\n Host: 10.0.0.42:8081\r\n Connection: close\r\n \r\n 99.443| client at 10.0.0.42:52003 expects to write to 10.0.0.42:8080 99.444| client at 10.0.0.42:52003 wrote 92 bytes to 10.0.0.42:8080 ( 92 bytes so far) 99.444| client at 10.0.0.42:52003 stops writing to 10.0.0.42:8080( after 92 bytes) 99.444| client at 10.0.0.42:52003 expects to read from 10.0.0.42:8080 99.444| client at 10.0.0.42:52003 read 284 bytes from 10.0.0.42:8080 ( 284 bytes so far) 99.445| client parsed response headers (269 bytes) HTTP/1.1 200 OK\r\n Date: Fri, 03 Jun 2005 22:33:50 GMT\r\n Content-Type: text/plain\r\n Last-Modified: Thu, 03 Jun 2004 22:32:10 GMT\r\n Cache-Control: public, " max-age=8,max-age=8 "=blah\r\n Content-Length: 15\r\n Via: 1.1 10.0.0.42:8081 (Apache/2.0.54)\r\n Age: 0\r\n Connection: close\r\n \r\n 99.445| expecting 15 bytes of message body based on Content-Length header 99.445| expected message body format: opaque message body 99.445| parsed 15 bytes of message body: body-efpnzpbjgm 99.445| client expects no more data (after 269 + 15 = 284 bytes) 99.445| content size: 15 99.445| client at 10.0.0.42:52003 stops reading from 10.0.0.42:8080( after 284 bytes) 99.445| client stops servicing connection with 10.0.0.42:8080 99.445| client at 10.0.0.42:52003 closing connection to 10.0.0.42:8080 (read 284 bytes and wrote 92 bytes) 99.446| server stops accepting HTTP queries at 10.0.0.42:8081 99.446| finished case: test_case/rfc2616/checkCached-fresh 99.446| result code: success 99.446| result reason: at the time of the request, entity instance appeared to be cached and fresh 99.446| sleeping for 10 seconds to increase age of a cached entity 109.447| *step 2.3*: verifying whether the cached entity is still cached /Subcase/: *check that a given entity instance is not cached or cached but stale* 109.447| starting sub-case test_case/rfc2616/checkCached-notORstale 109.448| server accepting HTTP queries at 10.0.0.42:8081 109.448| client connecting to 10.0.0.42:8080; 3 attempt(s) 109.448| client at 10.0.0.42:58593 connected to 10.0.0.42:8080 109.448| client will send 92 bytes (92 + 0) GET http://10.0.0.42:8081/thnnunshkgzi HTTP/1.1\r\n Host: 10.0.0.42:8081\r\n Connection: close\r\n \r\n 109.448| client at 10.0.0.42:58593 expects to write to 10.0.0.42:8080 109.449| client at 10.0.0.42:58593 wrote 92 bytes to 10.0.0.42:8080 ( 92 bytes so far) 109.449| client at 10.0.0.42:58593 stops writing to 10.0.0.42:8080( after 92 bytes) 109.449| client at 10.0.0.42:58593 expects to read from 10.0.0.42:8080 109.449| server at 10.0.0.42:8081 accepted connection from 10.0.0.42:61352 109.449| server at 10.0.0.42:8081 expects to read from 10.0.0.42:61352 109.449| server at 10.0.0.42:8081 read 130 bytes from 10.0.0.42:61352 ( 130 bytes so far) 109.450| server got request headers (130 bytes) GET /thnnunshkgzi HTTP/1.1\r\n Host: 10.0.0.42:8081\r\n Max-Forwards: 10\r\n Connection: close\r\n Via: 1.1 10.0.0.42:8081 (Apache/2.0.54)\r\n \r\n 109.450| expecting no message body 109.450| expected message body format: opaque message body 109.450| no more message body data to parse 109.450| server expects no more request data (after 130 + 0 = 130 bytes) 109.450| server at 10.0.0.42:8081 stops reading from 10.0.0.42:61352( after 130 bytes) 109.451| server will send 224 bytes HTTP/1.1 200 OK\r\n Cache-Control: public\r\n Last-Modified: Thu, 03 Jun 2004 22:32:10 GMT\r\n Cache-Control: " max-age=8,max-age=8 "=blah\r\n Content-Length: 15\r\n Date: Fri, 03 Jun 2005 22:34:01 GMT\r\n Connection: close\r\n \r\n body-efpnzpbjgm 109.451| server at 10.0.0.42:8081 expects to write to 10.0.0.42:61352 109.451| server at 10.0.0.42:8081 wrote 224 bytes to 10.0.0.42:61352 ( 224 bytes so far) 109.451| server at 10.0.0.42:8081 stops writing to 10.0.0.42:61352( after 224 bytes) 109.451| server stops servicing connection with 10.0.0.42:61352 109.452| server at 10.0.0.42:8081 closing connection to 10.0.0.42:61352 (read 130 bytes and wrote 224 bytes) 109.452| client at 10.0.0.42:58593 read 276 bytes from 10.0.0.42:8080 ( 276 bytes so far) 109.453| client parsed response headers (261 bytes) HTTP/1.1 200 OK\r\n Date: Fri, 03 Jun 2005 22:34:00 GMT\r\n Cache-Control: public, " max-age=8,max-age=8 "=blah\r\n Last-Modified: Thu, 03 Jun 2004 22:32:10 GMT\r\n Content-Length: 15\r\n Via: 1.1 10.0.0.42:8081 (Apache/2.0.54)\r\n Connection: close\r\n Content-Type: text/plain\r\n \r\n 109.453| expecting 15 bytes of message body based on Content-Length header 109.453| expected message body format: opaque message body 109.453| parsed 15 bytes of message body: body-efpnzpbjgm 109.453| client expects no more data (after 261 + 15 = 276 bytes) 109.453| content size: 15 109.453| client at 10.0.0.42:58593 stops reading from 10.0.0.42:8080( after 276 bytes) 109.453| client stops servicing connection with 10.0.0.42:8080 109.454| client at 10.0.0.42:58593 closing connection to 10.0.0.42:8080 (read 276 bytes and wrote 92 bytes) 109.454| server stops accepting HTTP queries at 10.0.0.42:8081 109.454| finished case: test_case/rfc2616/checkCached-notORstale 109.454| result code: success 109.454| result reason: at the time of the request, entity instance did not appear to be cached 109.454| finished case: test_case/rfc2616/ccRespDirMsg-max-age-obey 109.454| result code: success 109.454| result reason: cache did treat cached entity as stale when the age exceeds max-age Cache-Control directive 109.454| finished case: test_case/rfc2616/ccExtension-max-age-name-toClt 109.454| result code: violation 109.454| result reason: cache did not ignore max-age=8 in the name of blah=value extension response cache-directive ------------------------------------------------------------------------