Revision history [back]

Remember that the Host header is inserted by the CLIENT, so it reflects the server/port the client is attempting to reach.

Most load balancers CAN modify the Host header, but they must usually be configured to do so.

At first glance (and without examining the capture), your description suggests that the load balancer is accepting conversations on tcp/44006 and tcp/51006, and is NOT modifying the Host header...but only forwarding them to tcp/44006 on the destination system. I'm guessing that it looks something like this:

request1----->tcp/44006----\ |--load balancer----tcp/44006---->destination request2----->tcp/51006---/

So, in some cases the unmodified Host head from the original request doesn't match how the load balancer handled the conversation.

I think you need to talk with your load balancer team and review its configuration for your service. You probably need a load balancer rule that basically says, "forward this conversation to the destination on the port specified in the Host header."

Remember that the Host header is inserted by the CLIENT, so it reflects the server/port the client is attempting to reach.

Most load balancers CAN modify the Host header, but they must usually be configured to do so.

At first glance (and without examining the capture), your description suggests that the load balancer is accepting conversations on tcp/44006 and tcp/51006, and is NOT modifying the Host header...but only forwarding them to tcp/44006 on the destination system. I'm guessing that it looks something like this:

request1----->tcp/44006----\ |--load request1----->tcp/44006---->--load balancer----tcp/44006---->destination request2----->tcp/51006---/request2----->tcp/51006-----------/

So, in some cases the unmodified Host head from the original request doesn't match how the load balancer handled the conversation.

I think you need to talk with your load balancer team and review its configuration for your service. You probably need a load balancer rule that basically says, "forward this conversation to the destination on the port specified in the Host header."

Remember that the Host header is inserted by the CLIENT, so it reflects the server/port the client is attempting to reach.

Most load balancers CAN modify the Host header, but they must usually be configured to do so.

At first glance (and without examining the capture), your description suggests that the load balancer is accepting conversations on tcp/44006 and tcp/51006, and is NOT modifying the Host header...but only forwarding them to tcp/44006 on the destination system. I'm guessing that it looks something like this:

request1----->tcp/44006---->--load balancer----tcp/44006---->destination request2----->tcp/51006-----------/

So, in some cases the unmodified Host head from the original request doesn't match how the load balancer handled the conversation.

I think you need to talk with your load balancer team and review its configuration for your service. You probably need a load balancer rule that basically says, "forward this conversation to the destination on the port specified in the Host header."

Remember that the Host header is inserted by the CLIENT, so it reflects the server/port the client is attempting to reach.

Most load balancers CAN modify the Host header, but they must usually be configured to do so.

At first glance (and without examining the capture), glance, your description suggests that the load balancer is accepting conversations on tcp/44006 and tcp/51006, and is NOT modifying the Host header...but only forwarding them to tcp/44006 on the destination system. I'm guessing that it looks something like this:

request1----->tcp/44006---->--load balancer----tcp/44006---->destination request2----->tcp/51006-----------/

So, in some cases the unmodified Host head conflict you see occurs because the (unmodified Host) header from the original request doesn't match how reflect the action(s) of the load balancer handled the conversation.balancer.

I think you need to talk with your load balancer team and review its configuration for your service. You probably need a load balancer rule that basically says, "forward this conversation to the destination on the port specified in the Host header."header." That rule can be probably be implemented without modifying the Host header...and you don't want to add work to that device unless absolutely necessary.