[2.1] allow for future expiration dates
As per YSlow recommendations (http://developer.yahoo.com/performance/rules.html#expires) future expiration dates ins tatic resources (along the ETAG) are good to increase performance.
Not everybody may want it, but a configuration option to override the cache expiration date for static components would be great.
As Play uses embedded Netty, in places like Heroku where Play manages areas like gzip or expiration date users that may run big sites really need this option to be exposed somehow.
PS: I'm not sure how to tag this as 2.1 suggestion, so I added the [2.1] header
Comments and changes to this ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »