Thanks kindly Leif, that did the trick! Quick question. I also have another public-facing server with about the same horsepower (dual 3.6ghz dual-core Xeon vs dual 3.8ghz dual-core Xeon). Do you think there would be any benefits to using/running TS for internal clients, using the public facing server (not behind the firewall), as opposed to the internal server running TS, which is behind a firewall/router?
Thanks again for you quick and straight-to-the-point help! ----- Original Message ----- From: "Leif Hedstrom" <[email protected]> To: [email protected] Cc: "Johnny Stork" <[email protected]> Sent: Tuesday, June 14, 2011 1:28:48 PM Subject: Re: Basic Caching Forward Proxy Configuration? On 06/14/2011 02:21 PM, Johnny Stork wrote: Please excuse the newbie questions. I am trying to setup TS on an internal server, to use as a basic caching forward proxy. Install went fine on the CentOS x64 box. I tried finding some basic configuration docs, but none could be found and some I found were not consistent. The settings I changed were: ##records.config: CONFIG proxy.config.proxy_name STRING 192.168.1.182 (TS server IP) CONFIG proxy.config.reverse_proxy.enabled INT 0 (not trying reverse proxy yet, only want forward) CONFIG proxy.config.http.cache.http INT 1 (enabled forward caching proxy) You also need to disable remap required: CONFIG proxy.config.url_remap.remap_required INT 0 <blockquote> ##remap.config: Note sure what should, if anything, go in here. One article suggested this: regex_map http://( .*) http://$1 </blockquote> You should not have to add any mapping rules to remap.config (see above config setting). Attached is a little "sample" script from our contrib perl area, that shows the settings I'd suggest (minimum) that you should modify for reverse proxy. -- leif
