New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Define store key and Etag generation #77

Open

seivan opened this issue Dec 6, 2012 · 0 comments

seivan commented Dec 6, 2012

Is there a way to define how etags are generated and what key is being used to store it?

It would make expiration much easier when fine granular expiration is necessary without Rails.cache.clear.

Right now Etags are not being used for the memcache store, but something called X-Content-Digest.
Why is that?

EDIT; I found out about cache_key. Wondering if there is a way to do this in the controller/model level instead of a configuration.

Example;
fresh_when :etag => @jobs.maximum(:updated_at)
So before an update, I can clear memcache with @jobs.maximum(:updated_at)

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