The proc wasn't necessary in my testing. 

A proper request (to / or /dashboard) rendered with caching. 

A malformed request (/foo.png) rendered a 406 with no cache hit. 

This logic is fine, since caching is in an around filter and happens after the respond_to executes.