rack-cache icon indicating copy to clipboard operation
rack-cache copied to clipboard

Real HTTP Caching for Ruby Web Apps

Results 36 rack-cache issues
Sort by recently updated
recently updated
newest added

Hello! I have a question about the behaviour surrounding clearing the `Set-Cookie` header introduced here https://github.com/rtomayko/rack-cache/pull/52 From what I saw when testing this, cookies of any middleware inserted _after_ rack...

Hi guys! We currently use rack-cache in production and we are quite happy with it. We discovered the `stale_while_revalidate` flag for `expires_in` in rails (https://api.rubyonrails.org/classes/ActionController/ConditionalGet.html#method-i-expires_in). Is there any chance rack-cache...

we are using jruby-9.2.4 with rails 5.2.2 and rack-cache 1.8.0 and are currently facing this issue ``` cache error: undefined method `upcase' for nil:NilClass /Users/fady/.rvm/gems/jruby-9.2.4.0/gems/rack-cache-1.8.0/lib/rack/cache/storage.rb:36:in `create_store' /Users/fady/.rvm/gems/jruby-9.2.4.0/gems/rack-cache-1.8.0/lib/rack/cache/storage.rb:18:in `resolve_metastore_uri' /Users/fady/.rvm/gems/jruby-9.2.4.0/gems/rack-cache-1.8.0/lib/rack/cache/context.rb:34:in `metastore'...

Versions >1.7.2 breaks on rails 1.9 but changelog does not say that this will happen.

PR welcome ... see https://github.com/rtomayko/rack-cache/pull/135 basically needs some tmp object we can write to and then read from so we avoid that double read bug ... should be a nice...

I can see that no changes or pull request has been accepted in a long time. However would you be interested in a pull request that implemented a simple way...

The title says everything. When I send a GET request to the server, containing an `If-None-Match` header that matches the `ETag`, I get a `304 Not Modified` response as expected....

Hello, I think it would be a good idea to support the ConnectionPool (same author as Dalli) as the storage instance. I was pointed to this https://github.com/rtomayko/rack-cache/blob/master/lib/rack/cache/storage.rb#L41-L52 so I hacked...

In some cases it makes sense to have multiple resources for the same URL, e.g. one for logged-in and one for anonymous users. I believe the spec supports this, as...

If an EntityStore for a given entry was purged at the cache level--due to its native ttl--the corresponding MetaStore entry should be allowed to be purged as well.