Headers setting support when files match a regex #19
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
|
Thanks for this pull request and your interest in our project. Currently, we have some in-devel code in the working branch. At this time, we need to validate your code works with what exists in the working branch. Can you open a pull request against the working branch? |
|
Sure, here it is #20 |
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.
Sometimes it might be useful being able to assign to a file a specific header to be returned by RackSpace when serving the file to the clients.
E.g. it is useful for font files that sometimes need to include an
Access-Control-Allow-Origin: *header in order to be accessible cross-domain.This PR tries to add to posthaste a functionality similar to the one provide by Django-cumulus headers (http://django-cumulus.readthedocs.org/en/latest/#headers).