Comment 1 for bug 174204

So the basic steps we have are:

 1. extend LibraryFileAlias to store the Content-Encoding. As part of the database patch, update existing LibraryFileAlias rows with a filename like buildlog_*.txt.gz to use gzip encoding.
 2. make the librarian send a Content-Encoding header.
 3. extend the librarian upload protocol STORE method to accept a Content-Encoding header, and store it in the database (basically the same as what it does for Content-Type).
 4. update the librarian client classes to support setting the Content-Encoding.
 5. update Soyuz to tell the librarian that its build logs are gzip compressed.
 6. as part of the rollout, make sure the AddEncoding apache.conf directive is removed.