Google App Engine上的Access-Control-Allow-Origin标头 [英] Access-Control-Allow-Origin header on Google App Engine

查看:138
本文介绍了Google App Engine上的Access-Control-Allow-Origin标头的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个托管在App Engine上的网站(python2.7)和一个关于子域的链接博客。我使用博客帐户上的共享资源。具体来说,我分享了我在CSS中导入的图标字体(下面的例子)。

I have a website hosted on App Engine (python2.7) and a linked blogger on the subdomain. I use shared resources on the blogger account. Specifically, I share icon fonts which I import in my CSS (example below).

@font-face {
font-family: "FontAwesome";
src: url('fonts/fonts/fontawesome/fontawesome-webfont.eot');
src: url('fonts/fonts/fontawesome/fontawesome-webfont.eot?#iefix') format('eot'),
url('fonts/fonts/fontawesome/fontawesome-webfont.woff') format('woff'),
url('fonts/fonts/fontawesome/fontawesome-webfont.ttf') format('truetype'),
url('fonts/fonts/fontawesome/fontawesome-webfont.svg#FontAwesome') format('svg');
font-weight: normal;
font-style: normal;
}

@ font-face导入适用于除Firefox之外的所有浏览器,允许跨源资源共享。

The @font-face import works in every browser except for Firefox which doesn't allow for Cross-Origin Resource Sharing.

如何更改App Engine上静态字体文件夹中的标题以使导入在Firefox中正确运行?

How do I change the header on my static fonts folder on App Engine to enable the import to work correctly in Firefox?

推荐答案

在我的app.yaml上添加了以下处理程序,并且导入现在可以在所有浏览器中正常工作。 b
$ b

Added the following handler to my app.yaml on app engine and the import now works fine in all browsers.

handlers:
- url: /fonts
  static_dir: fonts
  http_headers:
    Access-Control-Allow-Origin: "*"

这篇关于Google App Engine上的Access-Control-Allow-Origin标头的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆