Hi all,

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.


Best Wishes,

Jacky C.K Tsoi

On Fri, 2006-02-17 at 16:00 +0800, Jacky C.K Tsoi wrote:[...]

This was intentional behaviour, in order to support various redirection
mechanisms.

It is no longer the case in the 2.x series. Upgrading would solve your
problem.[...]

We've tested a little of version 2.0, but it seems that the CheckURL 
feature has been changed to RegEx of the whole URL and configuring it is 
more clumsy than in version 1.x which use qid and qval.

Is it possible to have some sample to show how to utilize the CheckURL 
feature more efficiently?

Thanks.




Robert Segall wrote:[...][...][...]