Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updating for ATS v5.0.0.

...

Please keep in mind the following only applies to creating a forward-only web proxy caching setup;
I'd document others but I use ATS purely on a personal basis.

The following lists the initial steps involved in getting a generic Traffic Server install ,
from default configurations into a working setup. Once that's completed, feel free
to see my tuning guide for more information on performance settings.All three Wiki pages use configuration examples from my running home Traffic Server setupup and running.


IP Address Listening And Ports

Unlike Apache HTTP Server, Traffic Server takes a little more work to get things up and running.
The following settings are all located in the main configuration file, which by default is
/usr/local/etc/trafficserver/records.config.

Specifically, the following directive should be set unless you want Traffic Server listening on
every possible interface:

Code Block
LOCAL proxy.local.incoming_ip_to_bind STRING [2601:d:4880:536c3:426c:8fff:fe3a:43f1]

Also, the next directive will tell Traffic Server which ports to listen on:

...

In this example, Apache Traffic Server will now listen on my home machine's public IP,
port  port 8080 for IPv6 only.

I was originally using localhost, but after looking at the
HTTP the HTTP proxy headers that ATS produced, I decided to be more specific.

DNS

Another step that's just a little different is specifying to Traffic Server which DNS servers to use.
It will NOT simply assume whatever is in /etc/resolv.conf is fine and run with that.

This directive allows you to set which DNS servers Traffic Server should use.
Most likely you'll use your own, I'm using Comcast's DNS:

Code Block
CONFIG proxy.config.dns.nameservers STRING [2001:558:feed::1] 75.75.76.76

...

Required Remapping

The Apache Traffic Server default install configures remmapping URL re-mapping as required.

This will not
allow not allow you to use trafficserver as a "forward" foward proxy until you disable it in records.config file or 
configure or configure remapping specifically for your needs.

Code Block
CONFIG proxy.config.url_remap.remap_required INT 0

IP

IP-based Access Control List

To setup basic security in your Traffic Server install, you'll have to configure a different file,
by default /usr/local/etc/trafficserver/ip_allow.config. If you've ever done firewall
work the theory is very similar...simply list to Traffic Server what is allowed,
followed by what is NOT allowed.

...