Misleading "Content-Encoding: gzip" header on downloads
Bug #173096 reported by
Steve McMahon
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Critical
|
Brad Crittenden |
Bug Description
When .tar.gz (or .tgz) files are downloaded, they are being sent with "Content-Encoding: gzip" headers that cause all browsers to unpack the file on download. Since the files keep their .tar.gz or .tgz filename extensions, this results in a situation that will confound many users.
Please note that this is not a MIME problem. There are no MIME headers in the server response for the download. Sending a MIME header indicating gzip would not be a problem.
IMHO, this is not the intended use of the "Content-Encoding" header.
Changed in malone: | |
assignee: | nobody → bradcrittenden |
importance: | Undecided → Critical |
milestone: | none → 1.1.12 |
status: | New → Confirmed |
Changed in malone: | |
status: | Confirmed → In Progress |
Changed in malone: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Our admins tell us that this is being done by the apache instance in front of the launchpadlibrar ian.net web server. We want to keep this behaviour when serving build logs; it's extremely useful for Ubuntu developers to be able to view build logs in their web browser with zero effor.t
We should be able to disable the mod_mime magic (or whatever) in apache, and explicitly set or not the encoding in the launchpadlibrar ian.net web server, as appropriate for the file being served. For files from the download service, we should never set Content-Encoding. For package build logs, we should set it.