After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 446146 - Content-Type should handle case insensitive strings
Content-Type should handle case insensitive strings
Status: RESOLVED DUPLICATE of bug 523271
Product: evolution
Classification: Applications
Component: Mailer
2.6.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-06-10 21:43 UTC by Øystein Gisnås
Modified: 2012-02-13 14:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Øystein Gisnås 2007-06-10 21:43:21 UTC
Please describe the problem:
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

Steps to reproduce:
1. Export email with PDF attachment to mbox
2. Hand-edit the mbox file so that Content-Type says "application/PDF" instead of "application/pdf"
3. Import mbox file
4. Right click imported email


Actual results:
There are no suggested application to open the file with

Expected results:
Evince is suggest as it does for the email with lowercase Content-Type

Does this happen every time?
Yes

Other information:
This bug was originally reported by Giuseppe Sacco at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=421672

I tried the same with a image/jpeg attachment, but didn't experience the problem then.
Comment 1 André Klapper 2012-02-13 14:17:29 UTC
This was fixed in bug 523271.

*** This bug has been marked as a duplicate of bug 523271 ***