What steps will reproduce the problem?
1. After two subsequent requests for the same resource, the response status
code is still 200.
What is the expected output? What do you see instead?
The expected response status code should be 304 (not modified), because the
ETag header is checked against the resource fingerprint.
Original issue reported on code.google.com by alex.obj...@gmail.com on 16 Nov 2010 at 9:01
Original issue reported on code.google.com by
alex.obj...@gmail.com
on 16 Nov 2010 at 9:01