Apache Traffic Server 4.2.1 is released
The Apache Software Foundation and the Apache Traffic Server project are pleased to announce the release of Apache Traffic Server v4.2.1! This is our latest stable release, and is immediately available for download at:
Upgrading from the previous v3.2 release to v4.x should be done with care, since the cache is not backwards compatible. This means upgrading will cause the cache to be reinitialized. More details on upgrading is available on the Wiki:
Upgrading from 4.1.x should be seamless.
There's a number of new features in this bug-fix release.Details are available at:
4.2.x will be the last minor version in the 4.x release and is a Long Term Support (LTS) release.
Apache Traffic Server 4.2.0 is released
There's a number of new features in this bugfix release. Details are available at https://cwiki.apache.org/confluence/display/TS/What%27s+new+in+v4.2.x.
Traffic Server Documentation now officially on ReadTheDocs
Today we have officially moved Apache Traffic Server's documentation over to Read the Docs.
We have worked for quite some time now to move all of our documentation to Sphinx and into the git repository. This makes it simpler for both developers and users to contribute documentation updates.
Perhaps my favourite feature of RTD is how versatile they are. We now build the HTML with the Reference documentation from the same source we build the man pages. We can output epub and PDF, which you can download from the site. Best of all: It looks perfect on mobile devices.
Enjoy our new docs: http://trafficserver.readthedocs.org/
Custom logs and identifying remap rules
In a recent project we worked on, we needed to add a custom log which also had to identify which exactly remap rule triggered. I think this is probably a worthwhile feature to add to ATS (see https://issues.apache.org/jira/browse/TS-2181), but there's an easy way using existing plugins to accomplish this. Using (for example) the header_filter.so standard plugin, you can setup a config for each remap rule that you wish to identify.
map http://www.example.com http://x.example.com @plugin=header_filter.so @pparam=id_a.config
Where id_a.config contains simply
[READ_REQUEST_HDR] @MapID =a_mapping=
In a custom log, you can then log this as
Voila! The trick here is that headers with the @ prefix are considered internal to ATS, and are removed before sending to servers or User-Agents.
v4.0.1 is finally here!
The Apache Traffic Server community is extremely pleased to announce the immediate availability of our next major release, v4.0.1! This is the culmination of a years worth of work on features and bug fixes. Some fun facts about this release:
- There are contributions from 59 individuals
- Over 1,300 commits
- 446 Jira tickets were closed
Upgrading from v3.0 or v3.2 to v4.0 should be done with care, since the cache is not backwards compatible. This means upgrading will cause the cache to be reinitialized. More details is available at the Upgrade to v4.0 wiki page. There's a number of new features in this release, the highlights from the Wiki includes:
- Assign URLs to specific storage units.
- HTTP transaction buffering control
- CPU thread affinity
- Cache empty documents
- Fast Range: request handling
- More plugin and remap overridable configurations
- Lifecycle hooks for plugins
- A couple of new plugins, including a gzip plugin
Finally, this release marks a new milestone in how we will manage future release. This is documented in our new release proposal, please take a look at it, but the basic points are
- We follow strict Semantic Versioning, ever release within a major version is guaranteed to be API, ABI, cache and functionally backward compatible.
- We promise to bump major version at the most once per year (annually)
- We will produce minor releases on a strict quarterly schedule: May, August, November and February.
- The Git master branch is intended to be kept stable and releasable at all times. This implies that master can be seen as the daily current development release, and there are no more official development releases.
On the behalf of the entire Apache Traffic Server community, we hope you find this release to be useful and rock solid!
Apache Traffic Server v3.2.5 Released
The Apache Software Foundation and the Apache Traffic Server project are pleased to announce the release of Apache Traffic Server v3.2.5.
This is primarily a maintenance release, fixing minor SSL issue, as well as some build issues to make our package maintainers lives easier. We encourage Traffic Server users to upgrade - and everybody else to try it out!
The source code is immediately available for download.
Squid binary log with unmapped URL
The Squid log format that we have by default in Traffic Server is a standard format that works well for proxies. It's also well supported by existing log analyzers etc. However, in some cases, where you map many domains to one origin server, the logs produced aren't particularly useful. Why? Because the default Squid log format logs the remapped URL, and not the original client URL. There is of course an easy way to fix this, using our custom log formats.
- Disable the original Squid log format, and enable the custom logs.
- Create the new Squid log format in logs_xml.config
CONFIG proxy.config.log.logging_enabled INT 3 CONFIG proxy.config.log.custom_logs_enabled INT 1 CONFIG proxy.config.log.squid_log_enabled INT 0
<LogFormat> <Name = "squid_unmapped"/> <Format = "%<cqtq> %<ttms> %<chi> %<crc>/%<pssc> %<psql> %<cqhm> %<cquuc> %<caun> %<phr>/%<pqsn> %<psct> %<xid>"/> </LogFormat> <LogObject> <Format = "squid_unmapped"/> <Filename = "squid"/> <Mode = "binary"/> </LogObject>
How Comcast built a CDN using Traffic Server
At the 2013 Content Delivery Summit, Jan van Doorn gave a really interesting talk about how Comcast built an open source content delivery network with Apache Traffic Server at its core. Both the video of the talk and the slides are online.
In the talk, Jan covers the major parts of the Comcast CDN: the cache, configuration management, content routing and utilization monitoring. This is a great overview for anyone who is interested in building a CDN. There's enough open source out there that this should be practical for almost any organization.
The static tiered caching support that Comcast developed for this project landed in the Traffic Server 3.3.4 release, so you can experiment with it today.
ATS v3.3.4 (developer) is released!
We've just finished the v3.3.4 release, and it's now available for immediate download. The announcement email is included below, but please take this out for a spin and make sure it's moving towards stability.
Apache Traffic Server v3.3.4-dev Released The Apache Software Foundation and the Apache Traffic Server project are pleased to announce the release of Apache Traffic Server v3.3.4-dev. This is our latest development release, and is available from http://trafficserver.apache.org/downloads This is primarily a bug release over v3.3.3-dev, with one major feature: The ability to assign disks to volumes, such that you can target content to specific drives (e.g. an SSD). Please take this out for a spin, and file bugs and problem reports. We need everyone to keep testing these -dev releases, as we move towards our next stable release (v3.4). We are unfortunately 4-6 weeks behind right now, and looking for a v3.4 release by mid to end of July. Sincerely, -- The Apache Traffic Server community
BarCamp in Denver, July 9-10th
From the mailing lists announcements:
It's our pleasure to announce the next US Apache Traffic Server BarCamp! It will be held in downtown Denver, gracefully hosted by Comcast. It's a two day event, going all day from July 9th to July 10th. We will work on code, share experiences, come up with clever ideas, and help anyone who has questions or problems. This is a "DevOps" event, so even if you are not a hard-code C++ template wizard, you can participate (so I'm definitely going to be there). Please RSVP to firstname.lastname@example.org before June 15th, we'll send more details with directions etc. once we have a better idea how many people are participating. A few of us living in Denver can help with accommodations and travel to and from the airport as necessary. Sincerely, -- The Traffic Server PMC
Apache Traffic Server over 4% market share
Thanks to Go Daddy switching from IIS to Apache Traffic Server (good choice!) we're now at around 4.2% market share according to Netscraft's latest survey. We're combined with Apache in general, so we helped Apache gain one of the largest market share increases in recent history. The study is available at http://news.netcraft.com/archives/2013/05/03/may-2013-web-server-survey.html.
Apache Traffic Server 3.3.1 released
- gzip plugin is now configurable per mime-type
- Internal milestone timers exposed through plugin APIs
- In clustering mode, content can be forced to be cached locally
- A new authorization proxy plugin
- The FreeBSD builds now support raw disk caches
Traffic Server hackathon at ApacheCon 2013
ApacheCon will be hosting the conference hackathon on Monday February 25th, and the Traffic Server team will be there. There will be almost a dozen Traffic Server committers in attendance. We will be discussing the Traffic Server feature roadmap, hacking on bugs and generally trying to make Traffic Server better. Come by and tell us about your favorite bug (or feature)!
Apache Traffic Server 3.2.4
This is primarily a bug fix release, addressing a number of SSL related issues. Additionally we have important fixes which make running ATS on FreeBSD an overall more pleasant experience. We encourage Traffic Server users to upgrade - and everybody else to try it out!
The source code is immediately available for download.