Bug #10458 Invalid Content-Type header in bugs.mysql.com email
Submitted: 9 May 2005 7:05 Modified: 9 May 2005 7:17
Reporter: Marko Mäkelä Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Websites: bugs.mysql.com Severity:S3 (Non-critical)
Version: OS:
Assigned to: CPU Architecture:Any

[9 May 2005 7:05] Marko Mäkelä
Description:
The bugs.mysql.com content appears to be UTF-8 encoded now. However, this is not reflected by the MIME Content-Type header. The "NoF" message I got for Bug #9673
says "Content-Type: text/plain; charset=CHARSET" instead of the more appropriate "Content-Type: text/plain; charset=UTF-8".

How to repeat:
Make sure your name or the bug report contains non-ASCII characters. Examine the message sent by the bug database. Is the charset declared in Content-Type valid? Does the content correspond to it?

Suggested fix:
s/CHARSET/UTF-8/g
[9 May 2005 7:17] Jim Winstead
This is now fixed. Thanks for the report.