OSS TanbouOverview
Apache Traffic Server is a high-performance proxy server for forward proxying, reverse proxying, and HTTP caching. It can sit in CDN and large-scale web delivery paths and be extended through plugins.
Features and best fit
Based on official documentation; not hands-on tested · Content checked:
Combine forward/reverse proxying with HTTP caching
Traffic Server can broker outbound traffic as a forward proxy or sit in front of origins as a reverse proxy while caching responses for reuse.
Extend delivery behavior through plugins
Plugin APIs allow infrastructure-specific behavior to be added around the core proxy and caching engine.
Sources: [2]
For CDN and high-traffic web delivery layers
It fits infrastructure that needs to reduce origin load or bandwidth while proxying and caching large volumes of HTTP traffic.
Sources: [3]
Design cache policy and network failure behavior, not just process startup
Deployment requires decisions about proxy role, cache scope, origin routing, TLS, logging, and failure handling before production use.
Sources: [3]
Official sources
- [1]apache/trafficserver repository(2026-09-21)
- [2]Apache Traffic Server README(2026-09-21)
- [3]Apache Traffic Server Getting Started(2026-09-21)
- [4]Apache Traffic Server license(2026-09-21)
Supplemental curator note
Traffic Server is more than an HTTP cache: it combines forward/reverse proxy roles with plugin extensibility for network infrastructure. The README notes that version 10 moved the build system to CMake. Production design still needs explicit cache policy, origin routing, TLS, logging, and failure behavior.
Try it in 3 steps
- 1
Configure the CMake build
Follow the version 10+ README and configure an out-of-source build directory.
cmake -B build - 2
Build Traffic Server
Compile Traffic Server and its related components from the configured build directory.
cmake --build build - 3
Run the test suite
Run the README test step to validate the build. Production proxy and cache configuration belongs in the Getting Started workflow.
cd build && ctest
Growth
Growth trends · Last 30 days
1,985 Stars
Trend data is still being collected.
Development activity
Last 90 days · weekly
- Commits (last 30 days)
- 92
- Open PRs
- 73
Development activity is still being collected.
Built with
Categories and tags
Categories
GitHub data
GitHub dataView detailed GitHub data
GitHub Topics
- proxy
- cdn
- cache
- apache
- hacktoberfest
- forwardproxy
- http2
- http3
- quic
- reverseproxy
- Stars
- 1,985
- Forks
- 877
- Watchers
- 149
- Open issues
- 227
- Contributors
- 220
- Primary language
- C++
- License
- Apache-2.0
- Repository last updated
- Sep 21, 2026
Related information
Write a related articleShare a guide or use case for this OSS in Markdown. Articles are published after administrator approval.
Explore next
- curl42,891 Stars
1 shared tag(s) · 1 shared category(s)
A command-line data-transfer tool and embeddable libcurl library supporting HTTP(S), FTP, SFTP, SMTP, MQTT, WebSocket, and many other URL-based protocols.
C - Netty35,062 Stars
1 shared tag(s) · 1 shared category(s)
An event-driven asynchronous Java networking framework for high-performance protocol servers and clients.
Java - NGINX31,699 Stars
1 shared tag(s) · 1 shared category(s)
A server for web delivery, reverse proxying, load balancing, API gateways, and content caching.
C - Zen4,229 Stars
1 shared tag(s) · 1 shared category(s)
A cross-platform privacy guard that runs as a system-wide proxy to inspect HTTP/HTTPS traffic and block ads, trackers, malware, and unwanted requests beyond the browser.
Go - Axios109,206 Stars
1 shared tag(s)
A Promise-based HTTP client for browsers and Node.js with interceptors, adapters, cancellation, and transport controls.
JavaScript
Report incorrect information
Tell us if any listing information is incorrect or outdated.