Configure EmberCli::Deploy::File
cache headers
#403
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #401.
Previously, requests for Ember assets were being proxied through
EmberCli::Deploy::File
Rack middleware without the HTTPCache-Control
header.Ember
production
builds digest the filenames of images/css/js/etc.This makes these files highly cachable.
This commit configures the underlying
Rack::File
middleware to serveassets with the
Cache-Control
header set by Rails.