Request header field * is not allowed by Access-Control-Allow-Headers in preflight response

最新推荐文章于 2024-05-30 10:18:34 发布

凡尘只影

最新推荐文章于 2024-05-30 10:18:34 发布

阅读量1.7w

点赞数 1

CC 4.0 BY-SA版权

分类专栏： nginx Web前端文章标签：跨域 preflight Allow nginx header

本文链接：https://blog.youkuaiyun.com/u014481096/article/details/79792583

Web前端同时被 2 个专栏收录

15 篇文章

订阅专栏

nginx

6 篇文章

订阅专栏

本文介绍了解决跨域问题的方法，特别是在请求headers中添加自定义header时遇到的问题。通过在nginx配置文件中添加特定header来允许自定义header，从而实现跨域访问。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

跨域问题记录：请求 headers里添加自定义header时，出现以下错误

错误原因

参考：https://www.cnblogs.com/cc299/p/7339583.html

解决方法如下

nginx 配置 add_header 'Access-Control-Allow-Headers' 添加自定义header

add_header 'Access-Control-Allow-Headers' 'DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,access_token';

确定要放弃本次机会？

福利倒计时

: :

立减 ¥

普通VIP年卡可用

立即使用

凡尘只影

关注关注

1
点赞
踩
3

收藏

觉得还不错? 一键收藏
1
评论
分享

复制链接

分享到 QQ

分享到新浪微博

扫一扫
举报

举报

专栏目录

解决：Request header field token is not allowed by Access-Control-Allow-Headers in

是日已过，命亦随减的博客

09-28

4813

在入口文件index.php中添加 header('Access-Control-Allow-Origin: *'); header('Access-Control-Allow-Methods: GET, POST, PATCH, PUT, OPTIONS, DELETE'); header('Access-Control-Allow-Headers: *'); 其他添加过的地方全部删除，否则会重复。如果以这种方式添加则不会生效： $header['Access-Control-Allow-Origin

Request header field authorization is not allowed by Access-Control-Allow-Headers in preflight respo

达拉崩巴斑得贝迪卜多比鲁翁_

06-29

7108

在axios请求中出现：问题描述：如下图展示，在请求接口的时候，第一个接口返回200，但是第二个接口却返回0。上图是请求日本的域名，然而请求国内的域名是没有问题的。下面对比一下日本预检请求截图代码里设置了header 的请求截图（会报CORS错误）设置header信息的代码注释掉重新请求对比之后不难发现，多了一个Authorization 然后看一下nginx里请求头部的配置发现是没有允许Authorization的。由于接口需要在头部header传递Authori

1 条评论您还未登录，请先登录后发表或查看评论

Request header field Authorization is not allowed by Access-Control-Allow-Headers in preflig问题解决

阿牛哥的博客

10-18

3931

Request header field Authorization is not allowed by Access-Control-Allow-Headers in preflig问题解决

Request header field * is not allowed by Access-Control-Allow-Headers in preflight response问题解决

古柏树下的博客

06-13

3万+

跨域问题报错信息为：Failed to load http://localhost:8080/jfly.openapi/produce/listMachFeedingBoard/v1: Request header field Content-Type is not allowed by Access-Control-Allow-Headers in preflight response. ...

Request header field xxxx is not allowed by Access-Control-Allow-Headers in preflight response问题

weixin_45203607的博客

06-08

4800

这是因为目标服务不允许在请求头中加 x-run-as 这个第一种,前端请时候将请求头中的 x-run-as 这个去掉第二种,后端跨域配置中的请求头中添加这个key

Java Web 跨域设置

qq_37377082的博客

12-03

369

设置全局过滤器 import javax.servlet.*; import javax.servlet.annotation.WebFilter; import javax.servlet.http.HttpServletResponse; import java.io.IOException; /** * 跨域配置 * @author lijinghua */ @WebFilter(urlPatterns = {"/*"}) public class CorsFilter implements

CROS 预检请求异常解决方法 authorization is not allowed by Access-Control-Allow-Headers in preflight response

Tekin 是深耕技术 20 年的全栈实战派专家，精通 Go/Python/Java 等多语言开发。博客专注技术原理与实战结合，深度解析 Python 高阶编程、Go 语言架构、数据库优化等硬核内容。涵盖并发编程、机器学习、云原生等前沿领域，通过真实案例拆

05-30

762

CROS 预检请求异常解决方法 has been blocked by CORS policy: Request header field authorization is not allowed by Access-Control-Allow-Headers in preflight response.

ngxin Request header field authorization is not allowed by Access-Control-Allow-Headers in preflight response.

最新发布

03-18

用户提到的问题是在预检请求（preflight）的响应中，Access-Control-Allow-Headers没有包含Authorization头，导致请求被阻止。我需要找到正确的配置方法，确保Nginx在预检请求的响应中正确返回Authorization头。 ...

Request header field retoken is not allowed by Access-Control-Allow-Headers in preflight response.

07-27

这样就可以解决"Request header field retoken is not allowed by Access-Control-Allow-Headers in preflight response"的问题了。 #### 引用[.reference_title] - *1* *3* [Request header field token is not ...

thinkphp has been blocked by CORS policy: Request header field token is not allowed by Access-Control-Allow-Headers in preflight response.

12-20

ThinkPHP是一个基于PHP的开源Web开发框架，遇到"CORS policy: Request header field token is not allowed by Access-Control-Allow-Headers in preflight response"错误通常是由于跨域资源共享（Cross-Origin ...

Jeecms跨域 Request header field is not allowed by Access-Control-Allow-Headers in preflight response

tabvla的博客

03-17

1243

Jeecms框架，前后端分离二次开发，前端跨域报错Request header field is not allowed by Access-Control-Allow-Headers in preflight response

解决【Request header field bb is not allowed by Access-Control-Allow-Headers in preflight response.】问题

优快云wangjinwei的博客

06-06

1077

请求报头字段在响应中不被Access-Control-Allow-Headers允许，导致出现跨域导致。设置请求头,解决跨域问题。

跨域问题：Request header field token is not allowed by Access-Control-Allow-Headers in preflight response

小筱在线博客

05-23

5151

Access to XMLHttpRequest at 'http://xxxx' from origin 'http://yyyy has been blocked by CORS policy: Request header field token is not allowed by Access-Control-Allow-Headers in preflight response

完美解决nginx跨域问题Request header field x-token is not allowed by Access-Control-Allow-Headers in prefligh

Zisson_no_error的博客

08-03

1万+

Access-Control-Allow-Headers 响应首部 Access-Control-Allow-Headers 用于 preflight request （预检请求）中，列出了将会在正式请求的 Access-Control-Request-Headers 字段中出现的首部信息。简单首部，如 simple headers、Accept、Accept-Language、Content-Language、Content-Type （只限于解析后的值为 application/x-www-form-

Java过滤器配置类导致跨域问题：Request header field token is not allowed by Access-Control-Allow-Headers in prefli

ELSA001的博客

03-04

2564

Java过滤器配置类导致跨域问题：Request header field token is not allowed by Access-Control-Allow-Headers in prefli

blocked by CORS policy: Request header field token is not allowed by Access-Control-Allow-Headers in

Ggome的博客

05-11

6587

原因跨域设置没有设置token名称,将token加入请求跨域请求头里面即可。

Request header field content-type is not allowed by Access-Control-Allow-Headers（请求头设置问题）

icemwj的博客

08-07

6006

错误如上图。翻译过来就是：访问控制允许标题不允许使用请求标题字段内容类型。要么是自己设置的请求头信息不对，要么就是重复设置导致覆盖出错。检查自己在前后台交互的时候设置的请求头的相关信息，不要重复设置请求头信息(例如以下): res.header('Access-Control-Allow-Headers', 'Content-Type'); res.header('Access-Control-Allow-Headers', 'mytoken'); 对于同等级的请求头建议使用数组： r.

Request header field token is not allowed by Access-Control-Allow-Headers in preflight response.

八佾舞于庭

11-07

3799

报错 Request header field token is not allowed by Access-Control-Allow-Headers in preflight response. 报文：后台配置修改header为*,解决当前报错。

Request header field Content-Type is not allowed by Access-Control-Allow-Headers跨域