I am trying to write a template for my Blogger blog http://www.mostafa.info, I need to use a custom webfont.Everything goes well in IE and Chrome, but in Firefox that webfont won't render.
If you have a look at my blog with both firefox and chrome, you can see that font are different.
I searched a lot for the problem and I found out that the problem with Firefox is about cross-domain fonts. Those fonts must be hosted on my own Blogger blog (which is impossible!). And let me mention that I tested Google webfonts in Blogger and all went well!
But the question is how can this problem be solved?
Any kind of help will be appreciated.
I found a good way; I embed my webfonts into CSS using base64 like this:
#font-face{
font-family: "myFontName";
src: url(data:font/woff;base64,d09GRgABAAAAAGZ0ABEAA...AAA)
}
In this way It works in all browsers ;) and more important It is not necessary to have access to filesystem of server so I can host my CSS/Fonts on google sites
But the question is how can this problem be solved?
By having the server the fonts are hosted on send the right CORS headers to allow your blogger blog to access them.
Related
We send automatic emails to our customers.
Google is rewriting the email's image links and completely breaking them, giving a 404 error
Google is rewriting to:
https://ci5.googleusercontent.com/proxy/lVDjm7qabVoI9h7Coj2diPm68n9EGr70vaBDLDFWRsy4fPRbABMENW-f24JPGUgCWLdw7bPE5RvA5me4D9vVsS_pec0Xpc1uheArG_tIGk71Hjs=s0-d-e1-ft#http://www.example.com/image.png
404 error
So there is something wrong with the links that are being created by Google or the images are just not being uploaded to the googleusercontent server, but I have no idea how to solve the issue.
After much struggling, I discovered a solution for google injecting its own proxy server image URL.
For me, it was hosting the image privately (on my own server) that was causing the problem. After hosting the image publicly (on Mailchimp's Content Manager, for example) I was able to serve my images much more reliably.
I really hope this helps as it was causing me all kinds of problems.
Good luck!
I have this problem: Font awesome not working in Firefox
But no one there explained why there's a need to play with CORS settings even though the fonts are hosted on the same domain.
/index.html
/fonts/vendor/font-awesome/font-awesome.*
They're being imported using #font-face(). Works fine in Safari/Chrome.
One thing to keep in mind is this is being hosted on Heroku, but is also happening on localhost.
Again, the question is why do I have to allow access control even though the domain is the same?
I've been in the same trouble.
The fastest way is simply using the cdn link :
<link href="//maxcdn.bootstrapcdn.com/font-awesome/4.2.0/css/font-awesome.min.css" rel="stylesheet">
I really don't know exactly what's the problem but I read that happens because there's a CORS configuration issue.
I've just solved using the CDN
I am running a site. Some of its pages are not working in Firefox, but work perfect in Chrome. In Firefox it shows me a gray shield next to the URL and when I click on that shield and manually click on disable protection on this page then my page works fine. So now the problem is that there are many users on my site, and some of them don't know how to do it so I want to handle it on my site so its users don't need to do that.
How can I do it? I Googled and found a setting of Firefox in about:config named security.mixed_content.block_active_content. If we set it to false then it works. So is there a way to do it programmatically or other way so that users just view that page without seeing that shield?
As I understand it, content that is blocked by default by Firefox now is http content that is accessed from an https page. Common types of content that fall foul of this are external stylesheets and images.
As far as I am aware the way to prevent the problem on your site is to make sure that if a page is served by https, any and all other files that it references are also served by https.
Hi Friends,
The reason you see this error in Mozilla Firefox is because your
website is a Mixed Box that is, your website has many internal links
which are not SSL protected.
In order to avoid this error from showing up in Mozilla Firefox you
will have to make sure all the internal links on your website are SSL
protected.
So, Use https:// in your page not http://
I hope I was clear enough in answering your query.
firefox has blocked content that isn't secure means there are some contents on your website are not secure.
I had same issue as my fonts were downloading with http://google.apis.something instead of https
Then I change to //google.apis.something and problem get solved.
To know what is not secure in you website use this link
I am developing a website, which is currently running on my test server (IIS7). I can access the web site from any browser (including different versions of Firefox), but one specific Firefox does this:
http://www.mysite.com/www.mysite.com
I have no clue what to look for… Has anyone had such a problem?
You must have to have
link
or
link
but not
link
Some browsers do "smart" thing to correct these urls, but it's bad practice.
I've been searching for hours but can't seem to find an answer to this question. I have an https site that I'd like to display in a UIWebView. I can display simple sites like google in the webview but my https site is giving me no joy. I've tried ASIHTTPREQUEST and everything, but still no luck. Any help/code would be greatly appreciated.
Thanks,
Paul