Fix etag spec assumption
Fix etag spec assumption

Rack 2.2.0 sends an etag even if resource should not be cached.

This is ok since an etag is just a digest of the body and Rails
also sends a no-cache Cache-Control header for resources that must
not be cached.

Removing the test since we must not test internal Rack/Rails behavior.

robinboening/alchemy_cms,robinboening/alchemy_cms,AlchemyCMS/alchemy_cms,mamhoff/alchemy_cms,AlchemyCMS/alchemy_cms,robinboening/alchemy_cms,mamhoff/alchemy_cms,mamhoff/alchemy_cms,AlchemyCMS/alchemy_cms