Skip to content
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.

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

Use rack-cache 1.1 #3202

Merged
merged 2 commits into from Oct 3, 2011
Merged

Conversation

abscondment
Copy link
Contributor

Versions of rack-cache prior to 1.1 delete the If-Modified-Since and If-Not-Modified headers when
config.action_controller.perform_caching is true.

This creates two problems:

  • unexpected, inconsistent behaviour between development & production environments
  • breaks (production) applications that use of these headers -- really ungood for people trying to develop things that speak sensible HTTP.

I originally opened #3053 about this, but then discovered that Rails wasn't the culprit. The solution is upgrading to 1.1, which doesn't break anything as far as I could tell.

My test & changes are based off of master. I believe rack-cache 1.0.3 first appeared in some beta incarnation of 3.1, so it'd be good to get it into those branches if possible.

Versions prior to 1.1 delete the If-Modified-Since and If-Not-Modified headers when
config.action_controller.perform_caching is true. This has two problems:
 * unexpected inconsistent behaviour between development & production environments
 * breaks applications that use of these headers
josevalim added a commit that referenced this pull request Oct 3, 2011
@josevalim josevalim merged commit 1eac911 into rails:master Oct 3, 2011
@abscondment
Copy link
Contributor Author

Thanks! That was speedy :)

@josevalim
Copy link
Contributor

A great pull request with tests is very likely to be merged fast. ;) Thank
you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants