Mailing-List: contact users-help@trafficserver.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@trafficserver.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <4F2952A0.3080001@apache.org>
Date: Wed, 01 Feb 2012 07:56:32 -0700
From: Leif Hedstrom <zwoop@apache.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
 rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: users@trafficserver.apache.org
CC: "Alan M. Carroll" <amc@network-geographics.com>
Subject: Re: HTTP Headers in a forward proxy
References: 
 <CAHrNKxv=dG91MRS=vNV2LYS+PvEW-UpJ1iBmyvkKuhro4X3uPg@mail.gmail.com>
 <168908378.20120131221350@network-geographics.com>
 <E636467F-DD69-4DBD-B404-DA0929F303CD@apache.org>
 <1145144722.20120201082858@network-geographics.com>
In-Reply-To: <1145144722.20120201082858@network-geographics.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 2/1/12 7:28 AM, Alan M. Carroll wrote:
> I think it would be a good start, but the problem would be that he wanted this in a forward proxy. He would have to set up remap rules to trigger the header filtering only on the appropriate targets. I'm not sure if it would be simpler to tweak the plugin to check the URL or not.

Yeah. He could (as you said) create one (or a few) remap.config rules for 
youtube (he has to make sure remap.config is not required, but enabled via 
the reverse proxy config). E.g.

    map http://static.youtube.com  http://static.youtube.com 
@plugin=header_filter.so @pparam=youtube.config


or some such. Also remember he could use regular expressions here (on the 
host part). e.g.

    regex_map http://(.+)\.youtube\.(.+)  http://$1.youtube.$2 
@plugin=header_filter.so


(or some such, I don't know what the various youtube URLs looks like).

Cheers,

-- Leif