resolve/refinerycms — Issue #1207: Should Refinery be using Rack::Cache... twice?
Author: ms-ati
Created: 2012-01-05 04:15:46+00:00
State: open

When I create a Refinery CMS, and run `rake middleware`, I see that it's using Rack::Cache -- actually, twice:

```bash
$ refinerycms a_new_cms
...
$ cd a_new_cms
$ rake middleware
use ActionDispatch::Static \
use ActionDispatch::Static |
use ActionDispatch::Static |
use ActionDispatch::Static |
use ActionDispatch::Static |---- SIX OF THESE?
use ActionDispatch::Static |
use ActionDispatch::Static |
use ActionDispatch::Static |
use ActionDispatch::Static |
use ActionDispatch::Static /
use Rack::Lock
use Rack::Cache <---- #1
use Dragonfly::Middleware
use Rack::Cache <---- #2
use Dragonfly::Middleware
use Rack::Runtime
use Rails::Rack::Logger
use ActionDispatch::ShowExceptions
use ActionDispatch::RemoteIp
use Rack::Sendfile
use ActionDispatch::Callbacks
use ActiveRecord::ConnectionAdapters::ConnectionManagement
use ActiveRecord::QueryCache
use Dragonfly::CookieMonster
use ActionDispatch::Cookies
use ActionDispatch::Session::CookieStore
use ActionDispatch::Flash
use ActionDispatch::ParamsParser
use Rack::MethodOverride
use ActionDispatch::Head
use ActionDispatch::BestStandardsSupport
use Warden::Manager
run ANewCms::Application.routes
```

Is this intentional?
I noticed this while looking into why the HTTP Caching headers are disabled (#1206)