Mailing-List: contact users-help@trafficserver.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@trafficserver.apache.org
Received-SPF: pass (nike.apache.org: local policy)
From: Greg Smolyn <greg.smolyn@strangeloopnetworks.com>
To: "users@trafficserver.apache.org" <users@trafficserver.apache.org>
Date: Wed, 1 Sep 2010 12:52:19 -0700
Subject: Preventing host headers from changing in forward proxy mode
Thread-Topic: Preventing host headers from changing in forward proxy mode
Thread-Index: ActKDy+1QuNDD5F6QEaSxW3+YaW5+g==
Message-ID: <994E05D2-4BCA-41E0-93ED-19969FCD4875@strangeloopnetworks.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hi,=20
we've decided to use traffic server as a cache for a background process tha=
t does a bunch of fetching.  Admittedly we're doing something a bit non sta=
ndard, but we're having troubles trying to configure the system such that i=
t doesn't modify host headers on us.

Here's the scenario:
- trafficserver is listening on 127.0.0.1:8080
- we have a number of local VIPs on our machine that we use as aliases for =
real backend servers, so, if we want to fetch http://www.foo.com/test.jpg, =
we would go through it's VIP at, say, 10.0.1.1

What happens with trafficserver in the mix is:
- we open TCP connection to 127.0.0.1:8080 and does a GET http://10.0.1.1/t=
est.jpg with Host: www.foo.com
- trafficserver then requests on 10.0.1.1 a GET /test.jpg, with Host: 10.0.=
1.1

What we really need is the original Host header in the proxied request.

We've tried turning on proxy.config.url_remap.pristine_host_hdr (setting it=
 to 1), however this does nothing.

Any suggestions? Or are we going to have to write a plugin?  And if so, whi=
ch is a good plugin sample to start from?

Thanks!

-greg