如何解决Nginx代理-proxy_set_header-site.conf中的自定义标头用于Varnish缓存 信息我想做什么:原因: Varnishlog
是否可以在您的网站中发送自定义标头,然后使用proxy_set_header
将其转发到Varnish?
信息
我已经稍微移动了文件夹位置-正确包含了所有内容,并且可以正常工作。
我有/etc/nginx/conf.d/params/proxy.params/proxy_params
个文件,
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Port-Nginx $server_port;
proxy_set_header X-Forwarded-DocumentRoot $document_root;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Ssl-Offloaded $scheme;
proxy_set_header X-Forwarded-Custom-Location-Site 'Custom Site'; ### THIS IS THE HEADER I WANT TO BE DYNAMIC
fastcgi_param HTTPS on;
然后在sites-enabled/custom-site.conf
中的我的https服务器块中:
server {
listen 443 ssl default_server;
server_tokens off;
add_header 'Access-Control-Allow-Origin' '*';
add_header 'Custom-Location-Site' 'mysite1';
root /var/www/html;
server_name nginx-glo 192.168.1.105 localhost:443;
location / {
access_log /var/log/nginx/access.log main;
add_header 'Custom-Nginx-Server-Location-Root-Redirect' 'From /'; #### This header does not appear in varnishlog (testing only)
include /etc/nginx/conf.d/params/proxy.params/proxy_params_destination.conf;
相关的proxy_params_destination.conf
:
server_tokens off;
proxy_redirect off;
include /etc/nginx/conf.d/params/proxy.params/proxy_params;
# Try not to add headers using add_header,this will reset all headers from other locations
# that are redirected here.
# Also do not log to file here,log in locations above.
proxy_headers_hash_bucket_size 356;
proxy_read_timeout 3600;
proxy_connect_timeout 60;
# Cannot use https:// for proxy calls - use http,outside connection is https
proxy_pass http://varnish-cache-magento2.3.5:6081;
#proxy_pass http://web-server-apache2-magento2.3.5:8080;
我想做什么:
-
我已定义此标头:
add_header 'Custom-Location-Site' 'mysite1'
在网站conf文件中。 -
我想从每个网站的标题接收_value,并在此处转发:
proxy_set_header X-Forwarded-Custom-Location-Site $how_can_I_get_Custom-Location-Site_here;
,然后让Varnish缓存在vcl_recv{}
中接收此标头 -
然后我将在
vcl_recv{}
中处理此转发的标头:
使用以下示例中描述的req.http.X-Forwarded-Custom-Location-Site
。
原因:
为多个Magento 2网站设置清漆缓存。
- 以下Varnish文章中的示例显示了如何使用路径来实现。我无法使用路径,我有多个运行不同网站的Docker容器,然后将其转发到清漆容器。例如,运行
PHP 7.2
的Container和其他PHP 7.3
个网站都在/var/www/html,https
内运行
Link to sample multiple backends
样本中的相关部分:
sub vcl_recv {
if (req.url ~ "^/java/") {
set req.backend_hint = java;
} else {
set req.backend_hint = default;
}
}
backend default {
.host = "127.0.0.1";
.port = "8080";
}
Now let’s add a new backend:
backend java {
.host = "127.0.0.1";
.port = "8000";
}
Varnishlog
如此处所示:varnishlog
已在Docker容器中接收到我的自定义标头。我现在需要自定义标头的值是动态的。
- ReqHeader X-Real-IP: 192.168.1.103
- ReqHeader X-Forwarded-For: 192.168.1.103
- ReqHeader X-Forwarded-Port-Nginx: 443
- ReqHeader X-Forwarded-DocumentRoot: /var/www/html
- ReqHeader X-Forwarded-Proto: https
- ReqHeader Ssl-Offloaded: https
- ReqHeader X-Forwarded-Custom-Location-Site: Custom Site
解决方法
如果我理解正确,这就是您所需要的:
proxy_set_header X-Forwarded-Custom-Location-Site $http_custom_location_site;
这将根据您在X-Forwarded-Custom-Location-site
头中配置的server
块使Custom-Location-Site
动态。
例如,如果Custom-Location-Site
的值为mysite1
,则X-Forwarded-Custom-Location-site
的值将为:
X-Forwarded-Custom-Location-site: mysite1
根据http://nginx.org/en/docs/http/ngx_http_core_module.html#var_http_,您可以将$http_
与任何标题一起使用。您只需要小写该值,然后用下划线替换破折号即可。
版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。