1 個回答
- 最新
- 最多得票
- 最多評論
0
This means that you are not including Content-Type
in the list of headers included in the access-Control-Request-Headers
header in your HTTP OPTIONS request.
CORS can be complex - you need to reply to that OPTIONS request (a CORS PreFlight Request) with a response that includes a Access-Control-Allow-Headers
header that lists the headers out of Access-Control-Request-Headers
that you would allow to be used in future CORS requests.
Refer too https://fetch.spec.whatwg.org/#http-cors-protocol for detail on how this works.
相關內容
- 已提問 7 個月前
- AWS 官方已更新 3 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前