Request for member resource GET /member/1234
Host: www.example.com
HTTP/1.1 200 OK
Date: Tue, 16 Oct 2012 23:57:52 GMT
Expires: Wed, 17 Oct 2012 23:57:52 GMT
{"email":"[email protected] ", "password":"12345"}
The response expires in 24 hours
Update the email address of the member resource POST /member/1234
Host: www.example.com
{"email":"[email protected] "}
HTTP/1.1 200 OK
{"email":"[email protected] ", "password":"12345"}
Request from the proxy a new version of the object GET /member/1234
Host: www.example.com
Cache-Control: max-age=0
HTTP/1.1 200 OK
Date: Tue, 17 Oct 2012 00:10:12 GMT
Expires: Wed, 18 Oct 2012 00:10:12 GMT
{"email":"[email protected] ", "password":"12345"}
The presence of the Cache-Control header specifying max-age=0 in the request should force the proxy to revalidate with the origin server per RFC 2616
Same client makes a later request for the member resource GET /member/1234
Host: www.example.com
HTTP/1.1 200 OK
Date: Tue, 17 Oct 2012 03:05:03 GMT
Expires: Wed, 18 Oct 2012 00:10:12 GMT
{"email":"[email protected] ", "password":"12345"}
The request does not specify the Cache-Control header
The response has the same Expires header value as the previous response (cached at the edge)
The response has a Date header value that is older than the Expires header
