@Cached should respect the 'no-cache' policy #143

Closed
cescoffier opened this Issue Apr 11, 2014 · 0 comments

Comments

Projects
None yet
1 participant
@cescoffier
Member

cescoffier commented Apr 11, 2014

When a request has the +Cache-Control+ header set to +no-cache+, we should not return the cached value but call the action method. The result, however, can be cached (and replace the previously cached value).

@cescoffier cescoffier added this to the 0.5 milestone Apr 16, 2014

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