add support for r-maxage #55

Merged
merged 1 commit into from Jan 10, 2013

Conversation

Projects
None yet
3 participants
Contributor

fxn commented Feb 17, 2012

r-maxage is a new directive that takes precendence over s-maxage and
max-age.

While s-maxage is honored by any shared cache, r-maxage is only taken
into account by reverse proxy caches, and thus ignored by proxy and
private caches. Setting r-maxage allows applications to ensure the
response is only cached by their reverse cache, and thus are able in
particular to purge the cache knowing that it will not remain stale in
intermediate proxy servers.

@fxn fxn adds support for r-maxage
r-maxage is a new directive that takes precendence over s-maxage and
max-age.

While s-maxage is honored by any shared cache, r-maxage is only taken
into account by reverse proxy caches, and thus ignored by proxy and
private caches. Setting r-maxage allows applications to ensure the
response is only cached by their reverse cache, and thus are able in
particular to purge the cache knowing that it will not remain stale in
intermediate proxy servers.
1804e30

+1 to this. There are certainly times when I want intermediate caches to use a different s-maxage than Rack::Cache. r-maxage would be useful.

Owner

rtomayko commented Jan 10, 2013

Sorry for the massive delay here. Merging.

@rtomayko rtomayko merged commit 1804e30 into rtomayko:master Jan 10, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment