用于路由到终结点的 Azure 流量管理器自定义 Header
Azure Traffic Manager Custom Header for routing to endpoint
我有一个 multi-tenant SaaS 应用程序，它已经 运行 落后于 Azure 流量管理器（使用 Priority 方法配置）一段时间了。 （租户由子域标识，即 tenant1.mydomain.com、tenant1.mydomain.com 等）
现在我已经向我的 Azure 流量管理器添加了一个端点，并指定了一个 Custom Header Setting 如下：host:[tenantX].mydomain.com.
我的期望是 tenantX.mydomain.com 的所有请求现在都应该路由到我添加的新端点，但日志记录显示情况并非如此...所有请求仍将转到优先级 1端点。
我是不是遗漏了什么，或者这不是 Azure 流量管理器的自定义 Header 设置的用途？或者我应该改变路由方法吗？如果是这样，为了什么？
Custom Header settings are used to specify a host header ensuring that it hits the correct site when Traffic Manager performs health monitoring. It does not set which requests get routed to which endpoints. You only could define the routing methods via the six traffic-routing methods确定如何将网络流量路由到各个服务端点。
例如，在this blog中，你会看到它需要在自定义header设置下设置主机名，让大使知道它应该转发端点监控到Kubernetes集群中的哪个容器应用程序请求。
Custom header settings This configuration setting helps you add
specific HTTP headers to the health checks that Traffic Manager sends
to endpoints under a profile. The custom headers can be specified at a
profile level to be applicable for all endpoints in that profile and /
or at an endpoint level applicable only to that endpoint. You can use
custom headers for having health checks to endpoints in a multi-tenant
environment be routed correctly to their destination by specifying a
host header. You can also use this setting by adding unique headers
that can be used to identify Traffic Manager originated HTTP(S)
requests and processes them differently. You can specify up to eight
header:value pairs seprated by a comma. For example,
"header1:value1,header2:value2".
我有一个 multi-tenant SaaS 应用程序，它已经 运行 落后于 Azure 流量管理器（使用 Priority 方法配置）一段时间了。 （租户由子域标识，即 tenant1.mydomain.com、tenant1.mydomain.com 等）
现在我已经向我的 Azure 流量管理器添加了一个端点，并指定了一个 Custom Header Setting 如下：host:[tenantX].mydomain.com.
我的期望是 tenantX.mydomain.com 的所有请求现在都应该路由到我添加的新端点，但日志记录显示情况并非如此...所有请求仍将转到优先级 1端点。
我是不是遗漏了什么，或者这不是 Azure 流量管理器的自定义 Header 设置的用途？或者我应该改变路由方法吗？如果是这样，为了什么？
Custom Header settings are used to specify a host header ensuring that it hits the correct site when Traffic Manager performs health monitoring. It does not set which requests get routed to which endpoints. You only could define the routing methods via the six traffic-routing methods确定如何将网络流量路由到各个服务端点。
例如，在this blog中，你会看到它需要在自定义header设置下设置主机名，让大使知道它应该转发端点监控到Kubernetes集群中的哪个容器应用程序请求。
Custom header settings This configuration setting helps you add specific HTTP headers to the health checks that Traffic Manager sends to endpoints under a profile. The custom headers can be specified at a profile level to be applicable for all endpoints in that profile and / or at an endpoint level applicable only to that endpoint. You can use custom headers for having health checks to endpoints in a multi-tenant environment be routed correctly to their destination by specifying a host header. You can also use this setting by adding unique headers that can be used to identify Traffic Manager originated HTTP(S) requests and processes them differently. You can specify up to eight header:value pairs seprated by a comma. For example, "header1:value1,header2:value2".