Age header support
|Reported by:||Sergey Kandaurov||Owned by:|
- No Age response header in cached response (2616, 14.6):
An HTTP/1.1 server that includes a cache MUST include an Age header field in every response generated from its own cache.
- The upstream Age header value should be respected as well (2616, 13.2.3):
In essence, the Age value is the sum of the time that the response has been resident in each of the caches along the path from the origin server, plus the amount of time it has been in transit along network paths.
Note: See TracTickets for help on using tickets.