Librarian needs to store encoding
Bug #174204 reported by
Brad Crittenden
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
As discovered when analyzing bug 173096, files in the librarian should have the encoding as part of their metadata.
tags: | added: tech-debt |
Changed in launchpad-foundations: | |
status: | New → Triaged |
importance: | Undecided → Low |
To post a comment you must log in.
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.