...
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.
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 set unless you want Traffic Server listening on
every possible interface:
...
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.
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 for now use Hurricane Electric's Chicago DNSHere's an example of how to document config directives via the wiki:
Code Block |
---|
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 dns.nameservers STRING [2001:470:20::2] 74.82.42.42 |
Start It Up!
Code Block |
---|
sudo /usr/local/bin/trafficserver start
|
At this point you should have a workable, albeit very default web caching proxy server.
P.S. Please let me know if I've missed anything. It's been a while since I've done anything but tuning
so I might've left something out.