On 29/08/2014 01:35, Jorge Fábregas wrote:
Pound sends in the "X-Forwarded-For" header which you can use in Apache (& other apps) to see the original IP.
Ok, i changed the configuration files of both apache and drupal, and seems to work.

What about cascading pound?

I'm thinking to set up a new front-end running pound on a cloud server to provide a trouble free server move, the (temporary) scenario is:

a) configuring a new cloud server running pound which redirects to the old server, which runs pound ad some virtualized servers
b) move all domains dns records to the new frontend IP
c) mirror the hosted sites on the new cloud server
d) once all dns caches are updated, reconfigure pound on the cloud server to point his own virtualized servers
e) shut down the old server

in this case the pound front-end redirects to another pound front-end, is there any way to tell pound to take in account the "X-Forwarded-For" field if the connection comes from the first front-end IP?

I really hope my english was clear enought :)





--
To unsubscribe send an email with subject unsubscribe to [email protected].
Please contact [email protected] for questions.

Reply via email to