Traffic Server
Apache Traffic Server is a fast, modular, scalable and
extensible HTTP/1.1 compliant caching proxy server. It speeds internet
access, enhances the performance of a website, as well as delivering
web hosting capabilities. This software is a
high-performance building block for cloud services.
It is more than just a caching proxy server, as it also has support for
plugins to build large scale web applications.
Traffic Server is designed to improve content delivery for
enterprises, Internet service providers (ISPs), backbone providers, and
large intranets by maximizing existing and available bandwidth. Traffic
Server was formerly a commercial product
created by Inktomi and later aquired by Yahoo! in 2002. Yahoo!
maintained the source until its open source release in August 2009.
Features include:
- Proxying
- Receives user requests for web content as those requests
travel to the destined web server (origin server). If Traffic Server
contains the requested content, then it serves the content directly. If
the requested content is not available from cache, then Traffic Server
acts as a proxy
- provides explicit proxy caching, in which the user’s
client software must be configured to send requests directly to Traffic
Server
- Caching
- Reverse proxy
- Participate in flexible cache hierarchies, in which
Internet requests not fulfilled from one cache are routed to other
regional caches, thereby leveraging the contents and proximity of
nearby caches
- Supports ICP (Internet Cache Protocol) peering
- Network traffic analysis and monitoring:
- Traffic Line and Traffic Shell to collect and process
statistice obtained from network traffic information
- Transaction logging
- Security:
- Control client access to the Traffic Server proxy cache.
- Configure Traffic Server to use multiple DNS servers to
match your site’s security configuration. For example, Traffic Server
can use different DNS servers, depending on whether it needs to resolve
hostnames located inside or outside a firewall. This enables you to
keep your internal network configuration secure while continuing to
provide transparent access to external sites on the Internet
- Configure Traffic Server to verify that clients are
authenticated before they can access content from the Traffic Server
cache
- Secure connections in reverse proxy mode between a client
and Traffic Server, and Traffic Server and the origin server, using the
SSL termination option
- Control access via SSL (Secure Sockets Layer)
- Scales well on modern SMP hardware, handling 10s of
thousands of requests per second
- APIs to write your own plug-ins to do anything from
modifying HTTP headers to handling ESI requests to writing your own
cache algorithm
Return
to Web Caches Home Page
Last Updated Saturday, May 12 2012 @ 11:49 AM EDT
| 
