While the current administration guide is a great place to start when configuring Apache Traffic Server,
there are enough "gotchas" that I thought I'd contribute back to the project and document them.

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

The following lists the 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.

Both Wiki pages use configuration examples from my running home Traffic Server setup.

—

IP Address Listening And Ports

Unlike Apache HTTP Server, Traffic Server takes a little more work to get things up and running.

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

LOCAL proxy.local.incoming_ip_to_bind STRING 127.0.0.1 ::1

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

CONFIG proxy.config.http.server_ports STRING 8080:ipv6 8080

In this example, Apache Traffic Server will now listen on localhost, port 8080 for both IPv4 and IPv6.

TODO

• Update description.
• Add basic instructions for configuring IP address, and listen ports.
• Mention your habit of simply rebooting ATS for configuration changes.

Here's an example of how to document config directives via the wiki:

CONFIG proxy.config.http.flow_control.enabled INT 0
CONFIG proxy.config.http.flow_control.high_water INT 65536
CONFIG proxy.config.http.flow_control.low_water INT 65536