简体繁体 English

Github中Jekyll站点中的Access-Control-Allow-Origin HTTP标头

[英]Access-Control-Allow-Origin HTTP header in Jekyll site in Github

原文 2014-08-29 18:53:37 6 2 google-chrome/ jekyll

After upgrading to latest Google Chrome I'm getting the following error. 升级到最新的谷歌浏览器后，我收到以下错误。

Font from origin ' http://fonts.gstatic.com ' has been blocked from loading by Cross-Origin Resource Sharing policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. 来自“ http://fonts.gstatic.com ”的字体已被跨源资源共享策略阻止加载：请求的资源上没有“Access-Control-Allow-Origin”标头。

Because of this the web fonts are not working. 因此，Web字体无法正常工作。 I know that if I add Access-Control-Allow-Origin HTTP header it will work. 我知道，如果我添加Access-Control-Allow-Origin HTTP标头，它将起作用。 But my site is a Jekyll site and it is hosted in using Github. 但我的网站是一个Jekyll网站，它使用Github托管。

So how to add Access-Control-Allow-Origin http header in Jekyll generated site hosted in Github? 那么如何在Github中托管的Jekyll生成的站点中添加Access-Control-Allow-Origin http头？

2 个解决方案

Font in gstatic.com are served with Access-Control-Allow-Origin:* header. gstatic.com中的字体与Access-Control-Allow-Origin:*标头一起提供。 As stated here , it can be a proxy problem. 至于说在这里，它可以是一个代理问题。

One thing is sure, you can't set this header yourself on Github pages. 有一件事是肯定的，你不能在Github页面上自己设置这个标题。

This is an answer to an old question, but hopefully it will help someone. 这是一个老问题的答案，但希望它会帮助某人。

If you are accessing Google Maps API or Fonts using http, try using the https version instead. 如果您使用http访问Google Maps API或字体，请尝试使用https版本。

在plunker中没有'Access-Control-Allow-Origin'标题 - No 'Access-Control-Allow-Origin' header in plunker

javascript - Access-Control-Allow-Origin不允许使用Origin http://127.0.0.1 - javascript - Origin http://127.0.0.1 is not allowed by Access-Control-Allow-Origin

Chrome没有'Access-Control-Allow-Origin'标题，但标题就在那里 - Chrome saying No 'Access-Control-Allow-Origin' header, but the header is there

SAPUI5 中的 Access-Control-Allow-Origin' 标头错误 - Access-Control-Allow-Origin' header error in SAPUI5

如果 CORS 标头“Access-Control-Allow-Origin”为“*”，则不支持凭据 - Credential is not supported if the CORS header ‘Access-Control-Allow-Origin’ is ‘*’

随机得到没有'Access-Control-Allow-Origin' header 存在 - Randomly got No 'Access-Control-Allow-Origin' header is present

'Access-Control-Allow-Origin'标头包含多个值 - The 'Access-Control-Allow-Origin' header contains multiple values

请求的资源上不存在“Access-Control-Allow-Origin”标头？ - No 'Access-Control-Allow-Origin' header is present on the requested resource?

没有响应标头时允许CORS Access-Control-Allow-Origin - CORS allowed when no response header Access-Control-Allow-Origin

Access-Control-Allow-Origin不允许使用Origin？ - Origin is not allowed by Access-Control-Allow-Origin?

暂无

暂无

声明:本站的技术帖子网页，遵循CC BY-SA 4.0协议，如果您需要转载，请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 在plunker中没有'Access-Control-Allow-Origin'标题 - No 'Access-Control-Allow-Origin' header in plunker javascript - Access-Control-Allow-Origin不允许使用Origin http://127.0.0.1 - javascript - Origin http://127.0.0.1 is not allowed by Access-Control-Allow-Origin Chrome没有'Access-Control-Allow-Origin'标题，但标题就在那里 - Chrome saying No 'Access-Control-Allow-Origin' header, but the header is there SAPUI5 中的 Access-Control-Allow-Origin' 标头错误 - Access-Control-Allow-Origin' header error in SAPUI5 如果 CORS 标头“Access-Control-Allow-Origin”为“*”，则不支持凭据 - Credential is not supported if the CORS header ‘Access-Control-Allow-Origin’ is ‘*’ 随机得到没有'Access-Control-Allow-Origin' header 存在 - Randomly got No 'Access-Control-Allow-Origin' header is present 'Access-Control-Allow-Origin'标头包含多个值 - The 'Access-Control-Allow-Origin' header contains multiple values 请求的资源上不存在“Access-Control-Allow-Origin”标头？ - No 'Access-Control-Allow-Origin' header is present on the requested resource? 没有响应标头时允许CORS Access-Control-Allow-Origin - CORS allowed when no response header Access-Control-Allow-Origin Access-Control-Allow-Origin不允许使用Origin？ - Origin is not allowed by Access-Control-Allow-Origin?

相关标签

粤ICP备18138465号 © 2020-2024 STACKOOM.COM