add rack-cache.force-pass option #37

Merged
merged 2 commits into from Sep 11, 2011

Conversation

Projects
None yet
2 participants
@tekwiz
Contributor

tekwiz commented Sep 9, 2011

I have a need to optionally pass-through rack-cache. I have added the ability to set the rack-cache.force-pass env variable that can be set by a previous rack app, which forces rack-cache to pass through.

@rtomayko rtomayko merged commit 6943584 into rtomayko:master Sep 11, 2011

@rtomayko

This comment has been minimized.

Show comment
Hide comment
@rtomayko

rtomayko Sep 11, 2011

Owner

I'm kind of amazed there's not already some way to get that behavior. Can you tell me about the circumstances where you need this? I can think of a few cases but I'm curious as to what you ran into.

Owner

rtomayko commented Sep 11, 2011

I'm kind of amazed there's not already some way to get that behavior. Can you tell me about the circumstances where you need this? I can think of a few cases but I'm curious as to what you ran into.

@tekwiz

This comment has been minimized.

Show comment
Hide comment
@tekwiz

tekwiz Sep 11, 2011

Contributor

Thanks for merging this in.

There are 2 use cases that we have. First is testing: allowing a "secret" HTTP X-header or query variable to activate the force-pass variable. The second is to pass on specific versions of our application, for example, a "slow mobile" version which uses no javascript and therefore can't be cached when authenticated.

Contributor

tekwiz commented Sep 11, 2011

Thanks for merging this in.

There are 2 use cases that we have. First is testing: allowing a "secret" HTTP X-header or query variable to activate the force-pass variable. The second is to pass on specific versions of our application, for example, a "slow mobile" version which uses no javascript and therefore can't be cached when authenticated.

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