Inconsistencies in Content-Type returned for /readme.txt

[Kleidukos]

Some package have their /readme.txt content returned as text/plain; charset=utf-8, like text-show, and others have the content type set as text/plain, like cpsa.

I have two questions:

1. Where would this difference come from;
2. Couldn't we force all .txt files to be sent as text/plain; charset=utf-8?

Cheers

[gbaz]

mime matching is done here:

hackage-server/src/Distribution/Server/Framework/HappstackUtils.hs

Line 68 in b4ea1c7

mime :: FilePath -> String

txt falls through to the mimeTypes map from happstack, which should be just "text/plain" -- for some reason one of those readmes doesn't match that (not sure why!) so we get the default which also has the utf8.

We could add "txt" and "text" directly to customMimeTypes to override them and always ensure the utf8. A pr doing so would be welcome.

[Kleidukos]

Got it!