[Evolution] Bug#421672: Content-Type should handle case insensitive strings

Giuseppe Sacco giuseppe at eppesuigoccas.homedns.org
Mon Apr 30 23:01:58 UTC 2007


Package: evolution
Version: 2.6.3-6
Severity: normal

evolution does handle "Content-Type" field as case sensitive while
according to http://www.w3.org/Protocols/rfc1341/4_Content-Type.html it
shouldn't be case sensitive.

Currently, when I receive faxes using hylafax, the e-mail attachment
have this header:

Content-Type: application/PDF; name="fax000000179.pdf"
Content-Description: FAX Document (PDF)
Content-Disposition: attachment; filename="fax000000179.pdf"
Content-Transfer-Encoding: base64

and evolution doesn't offer to display the attachment using xpdf, but it
just offer to save the file.

If I change "application/PDF" to "application/pdf" then evolution
display the correct menu.

Bye,
Giuseppe




More information about the Pkg-evolution-maintainers mailing list