We've found that Pound will append a port number (the port number pound
is currently listening) to the "Host:" header of the request if it is
not specified in the original header.
The problem is that we've multiple pound instance listening in the same
machine, one of them is listening on port 82. And we use Firewall NAT
to forward incoming port 80 request to pound's port 82 with backend
listening on port 80.
So, while the client's request header is "Host: www.abc.com", it becomes
"Host: www.abc.com:82" when it arrives at the backend server, and since
the backend application rely on the host header to function, it could
not operate properly.
What I'd like to know is, is this behavior by design and what is the
purpose/reason of appending the port number?
Thank you so much.
Jacky C.K Tsoi