Closed Bug 345580 Opened 18 years ago Closed 9 years ago

Problem decoding quoted-printable question mark in subject

Categories

(Core :: Networking, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla47
Tracking Status
firefox47 --- fixed

People

(Reporter: christian, Unassigned)

Details

(Whiteboard: [necko-active])

Attachments

(2 files, 2 obsolete files)

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20060110 Debian/1.5.dfsg-4 Firefox/1.5 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20060110 Debian/1.5.dfsg-4 Firefox/1.5 When a subject contains only "Subject: =?ISO-8859-1?Q???=" Mozilla Thunderbird doesn't decode it and shows up as "=?ISO-8859-1?Q???=". The encoding is however legal with regards to RFC2045: 6.7 2) (Literal representation) Octets with decimal values of 33 through 60 inclusive, and 62 through 126, inclusive, MAY be represented as the US-ASCII characters which correspond to those octets (EXCLAMATION POINT through LESS THAN, and GREATER THAN through TILDE, respectively). Thank you, Christian Reproducible: Always Steps to Reproduce: 1. Create an .eml file containing: Return-Path: <christian@gmta.info> X-Original-To: razor@rapwap.razor.dk Delivered-To: razor@rapwap.razor.dk Message-ID: <44C20CC3.2070208@razor.dk> Date: Sat, 22 Jul 2006 13:32:19 +0200 From: Christian Joergensen <christian@gmta.info> Organization: razor.dk MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable To: christian@gmta.info Subject: =?ISO-8859-1?Q???= Testing. Subject should be: ? 2. Open it using file -> open saved message Actual Results: Subject: =?ISO-8859-1?Q???= Expected Results: Subject: ? Do not hesitate to contact me if there's any uncertainties in my bug report.
Hello? Is there anybody in there? :-)
I'm seeing the same problem. Anytime a question mark appears anywhere within a QP-encoded subject line, the decoding seems to fail and the subject line is presented in its encoded form.
I can reproduce this reliably in Shredder
Assignee: mscott → nobody
Status: UNCONFIRMED → NEW
Ever confirmed: true
Component: General → MIME
Product: Thunderbird → MailNews Core
QA Contact: general → mime
OS=all because I'm on Mac. per asuth, the responsible line of code appears to be at http://mxr.mozilla.org/mailnews/source/netwerk/mime/src/nsMIMEHeaderParamImpl.cpp#691
OS: Linux → All
Hardware: PC → All
Attached patch Patch v1 (obsolete) — Splinter Review
Assignee: nobody → justdave
Status: NEW → ASSIGNED
Attachment #334827 - Flags: review?
Attached patch Patch v2 (obsolete) — Splinter Review
eh, first one wasn't quite right.
Attachment #334827 - Attachment is obsolete: true
Attachment #334828 - Flags: review?
Attachment #334827 - Flags: review?
Attached patch Patch v3Splinter Review
Justdave was a little too trusting of my previous loop invariant suggestions :) I will attach a comm-central unit test that exercises this logic next. It's comm-central because nsIMIMEHeaderParam.idl marks decodeRFC2047Header noscript, and then the comment says that it's internal and MIME_DecodeMimeHeader is the only real consumer (apart from nsIMimeHeaderParam.getParameter). Since nsIMimeConverter in mailnews/mime exposes this functionality in a scriptable fashion that is straightforward (the method is decodeMimeHeader and explicitly takes a value), it seems like a nice unit testing substrate. In contrast, nsIMimeHeaderParam.getParameter does all sorts of crazy things.
Attachment #334828 - Attachment is obsolete: true
Attachment #334833 - Flags: review?(cbiesinger)
Attachment #334828 - Flags: review?
Attachment #334835 - Flags: review?(bienvenu) → review+
Assignee: justdave → bugmail
Component: MIME → Networking
Product: MailNews Core → Core
QA Contact: mime → networking
Version: unspecified → Trunk
biesi, are you the right person to review this for netwerk?
biesi, are you there?
bugmail is not a good way to reach me, in general. I could review this on Friday, or you can try to find someone else to review this in the meantime.
(In reply to comment #13) > bugmail is not a good way to reach me, in general. I could review this on > Friday, or you can try to find someone else to review this in the meantime. We should likely just move the code into comm-central from mozilla-central (cc'ing bienvenu). On a separate issue, should the module ownership listing for Necko be updated so that someone else is module owner (cc'ing bz)? (https://wiki.mozilla.org/Modules/Core still lists biesi)
Assignee: bugmail → nobody
Status: ASSIGNED → NEW
That's up to Christian. Note that the whole point of having module peers is that the owner may not be able to review everything. The owner _is_ supposed to have final call on technical issues.
Reviewing my comment about the module ownership, I realize it may be ambiguous. My intent was just to make sure that the module owner listing was accurate, not a statement of opinion about who should or should not be module owner. While I know some effort was made to clean up the module ownership listings, there are huge swathes of what I understand to be no-man's-lands where I think last-person-who-touched-it or has-any-clue-about-what's-going-on-in-there may have resulted in people being named, perhaps unwillingly. Having said that, it might helpful to mark those in the listing for the necko module who are more available to perform reviews / are actively checking their review request queue. I originally issued the review request in 2008 against biesi because I did not know enough about who was active in the project, etc., and assumed that the module owner would be likely to at least bounce the review at someone who could review it.
So some comments on module ownership and me :) There was a period of time where I did not really check my review queue, and that patch fell into that period. Recently I do check my queue and actively do reviews, but there are a fair amount of patches that are still left over in my queue. I really should deal with them in some way. I feel that I'm still a good choice for module owner, but if people disagree I could change it to someone else.
Comment on attachment 334833 [details] [diff] [review] Patch v3 Review of attachment 334833 [details] [diff] [review]: -----------------------------------------------------------------
Attachment #334833 - Flags: review?(cbiesinger) → review+
Whiteboard: [necko-active]
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla47
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: