# Install trafficserver with Homebrew, dnf, Nix, apt

HTTP/1.1 and HTTP/2 compliant caching proxy server. Version 10.1.4 via Homebrew; verified 2026-07-28. Also installable with nix: nix profile install nixpkgs#trafficserver.

## Install

```sh
sudo av install brew:trafficserver
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install trafficserver
```

  Evidence: local Homebrew formula metadata

### Linux

- dnf (92%):

```sh
sudo dnf install trafficserver
```

  Evidence: Fedora Rawhide package metadata: trafficserver from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/07190dc5ae9f35ae73866675fed6d95fe6e8d9fe22c9d7cdf85862cb2ed24a4c-primary.xml.zst

- Nix (92%):

```sh
nix profile install nixpkgs#trafficserver
```

  Evidence: nixpkgs package indexes: pkgs/by-name/tr/trafficserver/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

- Ubuntu apt (92%):

```sh
sudo apt install trafficserver
```

  Evidence: Ubuntu 24.04 LTS package indexes: trafficserver from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz

## Package facts

- **Package key:** brew:trafficserver
- **Package manager:** Homebrew
- **Version:** 10.1.4
- **Source summary:** HTTP/1.1 and HTTP/2 compliant caching proxy server
- **Homepage:** <https://trafficserver.apache.org/>
- **Repository:** <https://github.com/apache/trafficserver>
- **Last updated:** 2026-07-28T23:27:50Z
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- traffic_cache_tool (alias)
- traffic_crashlog (alias)
- traffic_ctl (alias)
- traffic_layout (alias)
- traffic_logcat (alias)
- traffic_logstats (alias)
- traffic_server (alias)
- traffic_top (alias)
- traffic_via (alias)
- trafficserver (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 10.1.4
## Project history and usage

Apache Traffic Server is a high-performance HTTP caching proxy and extensible proxy platform. Its modern open-source history begins with Yahoo's 2009 code donation to Apache, but its operational identity is as infrastructure for CDNs, large web properties, and traffic-heavy edge deployments.

### Project history

The Apache Traffic Server repository NOTICE states that the codebase was originally donated by Yahoo in 2009. GitHub repository metadata for the Apache mirror also dates the repository to October 31, 2009.

Apache's STATUS file records Traffic Server 2.0.0 as released on April 28, 2010, followed by a long sequence of major releases. The official site now presents Apache Traffic Server as a fast, scalable, extensible HTTP/1.1 and HTTP/2 compliant caching proxy server.

The project evolved from a caching proxy into a broader traffic platform. The official README calls it a high-performance building block for cloud services, with plugin support for large-scale web applications. The repository layout documents core binaries such as traffic_server, traffic_ctl, traffic_top, traffic_logstats, traffic_cache_tool, and plugin APIs.

### Adoption history

The official homepage says Apache Traffic Server powers major CDNs and content providers worldwide and serves multiple terabits per second of traffic. The official customers page lists use by companies ranging from startups to large Internet conglomerates, including Yahoo, Comcast, Akamai, LinkedIn, GoDaddy, and Yahoo Japan.

The NOTICE file also reflects sustained commercial participation, naming Yahoo, Network Geographics, OmniTI, Comcast, LinkedIn, GoDaddy, and others in contributed components. This makes the project unusual among packaged server tools: it is both a general open-source package and a production-hardened CDN/edge component.

### How it is used

Traffic Server is used as a forward or reverse HTTP proxy, cache, and extensible traffic layer. The official homepage emphasizes caching to reduce origin load and bandwidth, proxying, plugin APIs, modern protocol support, and high-throughput operation.

For operators and package users, the command surface is broad. Homebrew exposes tools such as traffic_server, traffic_ctl, traffic_top, traffic_logstats, traffic_logcat, traffic_cache_tool, traffic_layout, traffic_via, and traffic_crashlog. The official docs list configuration files including records.yaml, remap.config, cache.config, storage.config, logging.yaml, plugin.config, ssl_multicert.yaml, and sni.yaml.

### Why package nerds care

Apache Traffic Server is package-nerd significant because it is a heavy native C/C++ service with many optional system integrations, runtime tools, configuration files, plugins, and service-management expectations. Packaging it is closer to packaging a small platform than a single daemon.

It is also historically significant as Yahoo-origin infrastructure that became an Apache project and remained relevant in package managers for users who need local CDN-style caching, proxy experimentation, plugin development, or compatibility with large-scale traffic tooling.

### Timeline

- 2009: Yahoo-donated codebase appears in Apache Traffic Server's NOTICE and GitHub repository metadata.
- 2010: Traffic Server 2.0.0 released.
- 2011: Traffic Server 3.0.0 released.
- 2014: Traffic Server 5.0.0 released.
- 2018: Traffic Server 8.0.0 released.
- 2020: Traffic Server 9.0.0 released.
- 2026: Official documentation shows Apache Traffic Server 11.0.0.

### Related projects

- Yahoo, Comcast, LinkedIn, GoDaddy, OmniTI, Network Geographics, and Akamai appear in official Apache project materials as users or contributors.
- Traffic Server's plugin ecosystem and command-line tools are part of the official repository layout and administrator documentation.

### Sources

- <https://github.com/apache/trafficserver - official repository README and metadata.>
- <https://raw.githubusercontent.com/apache/trafficserver/master/NOTICE - official note that the codebase was originally donated by Yahoo.>
- <https://raw.githubusercontent.com/apache/trafficserver/master/STATUS - official release history.>
- <https://trafficserver.apache.org/ - official homepage with overview, scale, features, and documentation links.>
- <https://trafficserver.apache.org/users.html - official customers page.>


## Security Notes

broad file, network, media, or database tool signal.

- **Geiger risk:** blue / medium
- broad file, network, media, or database tool signal

## Other Package-Manager Records

- Nix - trafficserver: normalized package name match | nixpkgs package indexes: pkgs/by-name/tr/trafficserver/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
- Ubuntu apt - trafficserver - 9.2.3+ds-1+deb12u1build4: normalized package name match | Ubuntu 24.04 LTS package indexes: trafficserver from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz | fast, scalable and extensible HTTP/1.1 and HTTP/2.0 caching proxy server | https://trafficserver.apache.org/
- Ubuntu apt - trafficserver-dev - 9.2.3+ds-1+deb12u1build4: normalized package name match | Ubuntu 24.04 LTS package indexes: trafficserver-dev from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz | Apache Traffic Server Software Developers Kit (SDK) | https://trafficserver.apache.org/
- Ubuntu apt - trafficserver-experimental-plugins - 9.2.3+ds-1+deb12u1build4: normalized package name match | Ubuntu 24.04 LTS package indexes: trafficserver-experimental-plugins from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz | experimental plugins for Apache Traffic Server | https://trafficserver.apache.org/
- dnf - trafficserver - 10.1.1-2.fc45: normalized package name match | Fedora Rawhide package metadata: trafficserver from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/07190dc5ae9f35ae73866675fed6d95fe6e8d9fe22c9d7cdf85862cb2ed24a4c-primary.xml.zst | Fast, scalable and extensible HTTP/1.1 and HTTP/2 caching proxy server | https://trafficserver.apache.org/
- dnf - trafficserver-devel - 10.1.1-2.fc45: normalized package name match | Fedora Rawhide package metadata: trafficserver-devel from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/07190dc5ae9f35ae73866675fed6d95fe6e8d9fe22c9d7cdf85862cb2ed24a4c-primary.xml.zst | Development files for Apache Traffic Server plugins | https://trafficserver.apache.org/
- dnf - trafficserver-selinux - 10.1.1-2.fc45: normalized package name match | Fedora Rawhide package metadata: trafficserver-selinux from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/07190dc5ae9f35ae73866675fed6d95fe6e8d9fe22c9d7cdf85862cb2ed24a4c-primary.xml.zst | trafficserver SELinux policy | https://trafficserver.apache.org/


## Combined YAML source

View the package source record on GitHub. [combined/trafficserver.yml](https://github.com/mxcl/pkgdb/blob/main/combined/trafficserver.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph