Comments (2)
Yeah that makes sense to me. I'm curious, though, what other benefits would you want from rack-cache in that case? i.e., does it make sense to just remove rack-cache from the middleware pipeline entirely?
from rack-cache.
Right now removing rack-cache from the pipeline is the only option. The issue with that is your app may be returning public cache headers for content when inappropriate, but without an intermediary cache in dev/staging to surface the issue by returning the private/stale content you probably won't notice before promoting.
I considered the option of using ActionController#caches_page in dev and staging environments but 1) That's a fairly different request trajectory/code path so it's not really apples to apples 2) that mechanism is deprecated and has been removed from rails as of 4.1. and 3) It may well return 304 for fresh content as well for all I know.
The simple way to do this without touching rack-cache is to install a plugin before it in the pipeline that strips conditional get headers, but that is kind of a sledgehammer of an approach that won't work if your app needs to respond to those headers in some cases which is reasonable.
from rack-cache.
Related Issues (20)
- Problems with Dragonfly Gem after upgrading to 1.6.0 HOT 8
- Version 1.6.0 yanked? HOT 1
- Changelog is not up to date HOT 5
- reads from cache after writing, causing extra network roundtrip HOT 1
- Is it possible to use rack cache with HTTPS? HOT 3
- Publish 1.7 on Rubygems HOT 1
- Permission denied @ dir_s_mkdir - /var/cache HOT 5
- No files are stored HOT 3
- Resolve TODO - Purge metastore key when matching entitystore entry is not found
- >1.7.2 breaks on rails 1.9 HOT 2
- Bad cache entries trigger exception on v1.8.0 HOT 19
- content type
- undefined method `upcase' for nil:NilClass HOT 1
- feature request stale_while_revalidate HOT 1
- Move to rack org? HOT 11
- RuntimeError: can't add a new key into hash during iteration HOT 2
- Question about clearing `Set-Cookie` behaviour HOT 1
- Rake middleware display "use Module" instead of "use Rack::Cache" HOT 1
- Midldleware is displayed as Module rather than Rack::Cache on Rails 6.1.5 HOT 1
- No git tag since release 1.13.0 HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from rack-cache.