Nginx will definitely define it, and we can use it for what we need to know (what app name was this requester using, or "what name am I called," from the allowed hosts defined in the nginx vhost.)
I deployed a few services putting this setting and all of them are working perfectly. Just a question: in case I do not enable the "com.df.redirectWhenHttpProto", the "proto" property is still there in order to use it inside the service (for ex: nginx)? If not, I think that it ...
you will need something like X-FORWARDED-HOST to understand what hostname was used to connect to the API, because Apigee gets configured with whatever your backend DNS is, nginx and your app stack only see the Host header as your backend DNS name, not the hostname that was called in the...
I can get the correct behavior by setting the nginx header as: proxy_set_header X-Forwarded-Host $host:$server_port; and disablingUSE_X_FORWARDED_PORT. I take it thatX-Forwarded-Portis not popular, so maybe this bug is not worth fixing, but I will update my PR with a more explicit ...
host的值设置为$proxy_host,是指nginx.conf的proxy_pass中设置的host值,也就是192.168.1.3,也就是服务器的IP地址。 $http_host不是一个固定的变量,他其实是$http_HEADER通配后的结果。 $http_HEADER,注意,这里的HEADER是一个通配符,通配的是请求头里的header属性,例如$http_content_type表示请求头里content-type...