The Age field that we set in the header is not meant for consumption by end user browsers like Firefox, Chrome, Internet Explorer, etc. Rather, it's consumed by intermediaries. It actually has no effect on caching from the point of view of end users like yourselves.
The HTTP 1.1 specification is very clear on this:
The presence of an Age header field in a response implies that a response is not first-hand.
Source: http://www.w3.org/Protocols/rfc2616/rfc2616.html
- 7 Users Found This Useful