Refactor the way mime types are identified and set #4
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add RSpec specs. Dynamically override the Content-Type when necessary.
nbibler
added a commit
that referenced
this pull request
Jan 18, 2012
Refactor the way mime types are identified and set
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Due to the "recent" changes in Rack::Mime, the original method of optionally setting the mime types into Rack::Mime::MIME_TYPES is no longer working. This refactor creates a FontAssets::MimeTypes class which manages a local list of mime extensions and forcibly injects those types into font request content types.