#778772 use .txt extension on textual extracted files

Package:
tracker.debian.org
Source:
tracker.debian.org
Submitter:
Giuseppe Sacco
Date:
2015-12-12 08:18:05 UTC
Severity:
wishlist
#778772#5
Date:
2015-02-19 15:00:39 UTC
From:
To:
Hello,
while displaying changelog from the web interface I see that many
characters are not shown correctly because they have a different charset
than browser default.

Could you please specify the (utf8) charset in the HTTP response or
elsewhere?

Thanks,
Giuseppe
#778772#10
Date:
2015-02-22 17:30:25 UTC
From:
To:
Hi,

These files are served by apache, it appears the following line was
commented in the vhost host declaration:

  #AddDefaultChars utf-8

Problem might be text/html pages already have that header set by django,
we only want to apply the directive to plain text files. Should we
enclose that directive in a <Directory /path/to/media> section?

Christophe
#778772#15
Date:
2015-02-23 13:07:42 UTC
From:
To:
Hi,

Yes. I just did that:
$ HEAD https://tracker.debian.org/media/packages/0/0ad-data/changelog-0.0.16-1|grep Content-Type
Content-Type: text/plain; charset=utf-8

Shall we also possibly also consider using a .txt extension for all the
text files that we are extracting?

That would make it more future-proof. At some point, the files we are
extracting in media might also contain non-textual files...

Cheers,
#778772#20
Date:
2015-12-12 08:15:47 UTC
From:
To:
Control: retitle -1 use .txt extension on textual extracted files
Control: severity -1 wishlist

Repurposing this bug to track this as a wishlist. It's certainly cleaner
than relying on custom webserver configuration...

Cheers,