n8 / bust_rails_etags Goto Github PK

https://svbtle.com/rails-caching-a-problem-with-etags-and-a-solution

is dead.

New link:
http://ninjasandrobots.com/rails-caching-a-problem-with-etags-and-a-solution

We want to be able to turn off etags in dev env, but removing ConditionalGet or Etag from the Rack stack does not do it. As this issue points out (rails/rails#3583) they don't consider a feature they should support.

I felt the next best thing was to put this feature in this gem. I forked it and tried implementing it but couldn't get user initializers running before this gem gets inserted into the stack.

What are your thoughts on being able to disable etags in dev environment?

Hi @n8,

thank you for the idea to take the heroku version into account.
I came up with a slightly improved API call, which just returns the current release and not all of them.

  ENV['ETAG_VERSION_ID'] =
    Heroku::API.new(api_key: Figaro.env.heroku_api_key)
      .get_release(Figaro.env.heroku_app, :current)
      .body['name']

I also want to note, that this gem might be obsolete with Rails 4.
Rails 4 introduced controller-wide ETags.

class ApplicationController < ActionController::Base
  etag { ENV['ETAG_VERSION_ID'] }

  # ...
end