Hello,

I'm running Pound 1.8 and my pounf.cfg file contains:

---
ListenHTTP 10.0.0.1,80
User nobody
Group nobody
Loglevel 0
RewriteRedirect 1

UrlGroup ".*"
HeadRequire Host "foo\.domain\.tld.*"
BackEnd 10.0.0.1,1234,1
EndGroup

UrlGroup ".*"
BackEnd 10.0.0.1,81,9
EndGroup
---

I used tcpdump and ethereal to inspect the TCP traffic of ports 80, 81
and 1234 as it was seen on the server 10.0.0.1. The HTTP server
running on port 1234 receives the "X-Forwarded-for" header as
documented on the website. The HTTP server running on port 81 does
not.

Is there a configuration option I'm missing?

-Michal

On Wednesday 15 December 2004 21.04, Michal wrote:[...]

No, it should come to ports 1234 and 81 (certainly not 80 - that is where 
Pound listens). Are you completely sure the traffic to port 81 comes from 
Pound? The way you configured it, requests to foo.domain.tld would go to port 
1234 and everything else to 81. Try a request to http://10.0.0.1 to make 
sure.[...]

On Wed, 15 Dec 2004 21:24:31 +0100, Robert Segall <roseg(at)apsis.ch>
wrote:[...]

Yes, everything as I described it is correct. However, I was
inspecting packets in the "outer" envelope:

  client -> 10.0.0.1:80
  10.0.0.1:80 -> client

rather than the "inner" envelope:

  10.0.0.1:80 -> 10.0.0.1:81
  10.0.0.1:81 -> 10.0.0.0:80

So the X-Forwarded-for header does appear where it should (the inner).

Sorry for the commotion, but I've been through a lot to get pound
working with my setup and needed a bit more encouragement :) It's a
really neat tool. Thanks, Robert.

-Michal