charset=UTF-8 when serving non-base64 files
@takluyver does mimetype return the charset for a file? I wouldn't think it would, but for text/plain sending charset=utf-8 wouldn't be that bad of a guess in most cases.
When you have a .txt file and click on it in the browser, you open up an editor that correctly shows the contents as a UTF-8, it is only when you download the raw file at the moment, for example when you rename a file with UTF-8 characters within it to
Thanks, that looks good. There's a test failure, though, because we have a test that expects
I don't think mimetype - or anything in the standard library - does encoding detection.