p83822
February 20, 2012, 1:14pm
1
Got a third party who return headers like this (for 3 requests):
Cache-Control: public, no-transform, max-age=600
…
Cache-Control: public, no-transform, max-age=600
…
Cache-Control: public, no-transform, max-age=600
…
i.e. the Age header just keeps on going up.
I had kinda assumed that the Age ought to increment up to 600 (599?) and then start all over again with new Date and Expires values.
I want to get my facts straight before contacting the chaps about serving expired resources.
Much obliged.
N
p83822:
Got a third party who return headers like this (for 3 requests):
Cache-Control: public, no-transform, max-age=600
…
Cache-Control: public, no-transform, max-age=600
…
Cache-Control: public, no-transform, max-age=600
…
i.e. the Age header just keeps on going up.
I had kinda assumed that the Age ought to increment up to 600 (599?) T h i s i s a n e x c e l l e n t s i t e I love i t and then start all over again with new Date and Expires values.
I want to get my facts straight before contacting the chaps about serving expired resources.
Much obliged.
N
I have no idea about age header! I too would like to know the answer!
p83822
February 22, 2012, 7:07pm
3
Looks like we have a guffed Proxy server someone in the route which adds the Age header.
The response from ‘them’ (from their caching layer) has a decrementing max-age and, when it get’s to 0, a fresh response is served (new Date and Expires headers) with a full max-age.
Looks like I put this on the wrong thread and, arguably on the wrong forum. Apologies for this. I so regularly scramble my head with caching and it’s permutations and I know that users of this site know this stuff inside out.
BR
Neil
pmeenan
February 22, 2012, 10:27pm
4
I think you had a good place for the question just stumped all of us since what you were seeing didn’t make any sense
