gpt4 book ai didi

cors - Haproxy CORS No 'Access-Control-Allow-Origin' header is present on the requested resource

转载 作者:行者123 更新时间:2023-12-05 01:39:21 25 4
gpt4 key购买 nike

我想通过返回以下响应调用来配置 haproxy 来处理 CORS:

<Header name="Access-Control-Allow-Origin">*</Header>
<Header name="Access-Control-Allow-Headers">Origin, X-Requested-With, Content-Type, Accept, Authorization, JSNLog-RequestId, activityId, applicationId, applicationUserId, channelId, senderId, sessionId</Header>
<Header name="Access-Control-Max-Age">3628800</Header>
<Header name="Access-Control-Allow-Methods">GET, DELETE, OPTIONS, POST, PUT</Header>

但是,我得到的是“请求的资源上不存在‘Access-Control-Allow-Origin’ header ”。请注意,我使用的是 haproxy 1.7.9,无法使用 lua 进行编译。

我已经查看了 https://www.haproxy.com/blog/enabling-cors-in-haproxy/但不能用 lua 重新编译。

还有 HAProxy CORS OPTIONS header intercept setup

global
log 127.0.0.1 local0
log-send-hostname

chroot /etc/haproxy
pidfile /var/run/haproxy.pid
maxconn 40000
user haproxy
group haproxy

daemon
nbproc 2
tune.ssl.cachesize 100000
tune.ssl.default-dh-param 2048

defaults
log global
log-format %ci:%cp\ [%t]\ %ft\ %b/%s\ %Tq/%Tw/%Tc/%Tr/%Tt\ %ST\ %B\ %U\ %CC\ \ %CS\ %tsc\ %ac/%fc/%bc/%sc/%rc\ %sq/%bq\ %hrl\ %hs\ %{+Q}r
mode http
retries 3
timeout check 60s
timeout client 1m
timeout client-fin 10s
timeout connect 10s
timeout http-keep-alive 60s
timeout http-request 60s
timeout queue 1m
timeout server 1m
timeout server-fin 10s
option dontlognull
option forceclose
option forwardfor
option http-server-close
balance roundrobin

# Set up application listeners here.
resolvers dns
nameserver dns1 XXXXXXXXXXXXXXXXXXXXXXXXXX
resolve_retries 3
timeout retry 1s
hold valid 10s

frontend http_frontend
mode http
bind XXXXXXXXXXXXXXXXXXX:80 accept-proxy

capture request header Authorization len 64
.
.
default_backend dead_end

frontend https_frontend
mode http
bind XXXXXXXXXXXXXXXX:443 accept-proxy ssl crt /etc/haproxy/crt/ ssl verify optional ca-file /etc/haproxy/ca-file/ca-haproxy-stage.crt ciphers ECDHE-RSA-AES256-SHA:!RC4-SHA:!RC4:HIGH:!MD5:!aNULL:!EDH:!AESGCM no-sslv3

capture request header Host len 64
capture request header Authorization len 128
.
.
capture request header Content-Length len 64
capture request header Content-Type len 64


# BEGIN CORS

capture request header origin len 128

http-response add-header Access-Control-Allow-Origin %[capture.req.hdr(0)] if { capture.req.hdr(0) -m found }
rspadd Access-Control-Allow-Headers:\ Origin,\ X-Requested-With,\ Content-Type,\ Accept,\ Authorization,\ JSNLog-RequestId,\ activityId,\ applicationId,\ applicationUserId,\ channelId,\ senderId,\ sessionId if { capture.req.hdr(0) -m found }
rspadd Access-Control-Max-Age:\ 3628800 if { capture.req.hdr(0) -m found }
rspadd Access-Control-Allow-Credentials:\ true if { capture.req.hdr(0) -m found }
rspadd Access-Control-Allow-Methods:\ GET,\ DELETE,\ OPTIONS,\ POST,\ PUT if { capture.req.hdr(0) -m found }

# END CORS

use_backend bkservice


backend bkservice
mode http

option tcp-check
option log-health-checks
tcp-check connect port 80
tcp-check send GET\ /hap_health HTTP/1.0\r\n
tcp-check send \r\n
tcp-check expect rstring HTTP/1.0\ 200\ OK
server BK_SERVICE myservice.stage.com:443 ssl verify none sni str(myservice.stage.com) check resolvers dns

backend dead_end
mode http
server de 127.0.0.1:9001

在“https://myservice.stage.com/endpoint”访问 XMLHttpRequest '来自原产地' http://localhost:4200 ' 已被 CORS 策略阻止:对预检请求的响应未通过访问控制检查:请求的资源上不存在“Access-Control-Allow-Origin” header 。

最佳答案

如果您想允许所有内容,您可以删除配置中的 CORS block 并为每个响应设置所需的 header :

frontend https_frontend
...
# BEGIN CORS
http-response set-header Access-Control-Allow-Origin "*"
http-response set-header Access-Control-Allow-Headers "Origin, X-Requested-With, Content-Type, Accept, Authorization, JSNLog-RequestId, activityId, applicationId, applicationUserId, channelId, senderId, sessionId"
http-response set-header Access-Control-Max-Age 3628800
http-response set-header Access-Control-Allow-Methods "GET, DELETE, OPTIONS, POST, PUT"
# END CORS

但是您应该确保使用通配符适合您的服务。如果不是,那么找到一种方法来使用在 Lua 支持下编译的 HAProxy 可能是有意义的。

关于cors - Haproxy CORS No 'Access-Control-Allow-Origin' header is present on the requested resource,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/58422210/

25 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com