大网数据广告活动
服务器运维问答

Allowing all headers in CORS

· 52CE 我爱测

I want to configure my Apache 2.4 to serve some static resources in a CORS-friendly way. I already have the following setting: Header always set Access-Control-Allow-Origin "*" However, for recent Safari this appears to not be en…

问题原文

原帖链接 · MvG · CC BY-SA 3.0

I want to configure my Apache 2.4 to serve some static resources in a CORS-friendly way. I already have the following setting:

Header always set Access-Control-Allow-Origin "*"

However, for recent Safari this appears to not be enough:

[Error] Failed to load resource: Request header field … is not allowed by Access-Control-Allow-Headers.

Fields mentioned in this fashion include Accept-Encoding and DNT, but I guess after adding them I might also be seeing Cache-Control, Origin and Accept-Language, since these are the ones mentioned in the Access-Control-Request-Headers header sent by Safari. But who is to tell me what other headers Safari or some other browser might be requesting, now or in a future, for myself or for some other user with a different configuration? Apparently * is not a valid setting for the Access-Control-Allow-Headers header, for reasons I don't really understand.

So how do I configure a server to just say “use this resources anywhere, I don't care about CORS for them”?

已采纳解答

原帖链接 · dontcallmedom · CC BY-SA 3.0

* is now a valid value for Access-Control-Allow-Headers at least for non-credentialed requested; but since this is a fairly recent addition to the specification, it probably hasn't reached browsers yet.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2016-08-29)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。