Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changes response header in development, but not production? #30

Open
nozpheratu opened this issue Jun 18, 2014 · 1 comment
Open

Changes response header in development, but not production? #30

nozpheratu opened this issue Jun 18, 2014 · 1 comment

Comments

@nozpheratu
Copy link

I'm using the gems defaults to allow all font origins, and I can see the response header changing on my development environment. But when I push to production where I'm loading all of my assets from cloudfront I see that the allowed origin is still being set to my origin domain ID that I had setup when I created the Cloudfront distribution?

I'm using Rails 4.1.1. I also noticed that the mime type that gets registered in my Firefox network tab for the particular font asset I'm trying to load in from Cloud front is "font-woff", instead of just "woff". Not sure if that would have an effect on anything or not...

@nozpheratu nozpheratu changed the title Changes header in development, but not production? Changes response header in development, but not production? Jun 18, 2014
@anushamummina
Copy link

I am also getting the same issues, fonts are loading in development mode but not loading in production mode. Can anyone please help me on this. Thanks in Advance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants