Closed
Bug 345580
Opened 18 years ago
Closed 9 years ago
Problem decoding quoted-printable question mark in subject
Categories
(Core :: Networking, defect)
Core
Networking
Tracking
()
RESOLVED
FIXED
mozilla47
Tracking | Status | |
---|---|---|
firefox47 | --- | fixed |
People
(Reporter: christian, Unassigned)
Details
(Whiteboard: [necko-active])
Attachments
(2 files, 2 obsolete files)
1.15 KB,
patch
|
Biesinger
:
review+
|
Details | Diff | Splinter Review |
856 bytes,
patch
|
Bienvenu
:
review+
|
Details | Diff | Splinter Review |
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.
Reporter | ||
Comment 1•18 years ago
|
||
Hello? Is there anybody in there? :-)
Comment 2•18 years ago
|
||
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.
Comment 3•16 years ago
|
||
I can reproduce this reliably in Shredder
Assignee: mscott → nobody
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•16 years ago
|
Component: General → MIME
Product: Thunderbird → MailNews Core
QA Contact: general → mime
Comment 4•16 years ago
|
||
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
Comment 5•16 years ago
|
||
But I think he really means here:
http://mxr.mozilla.org/comm-central/source/mozilla/netwerk/mime/src/nsMIMEHeaderParamImpl.cpp#660
Comment 6•16 years ago
|
||
Comment 7•16 years ago
|
||
Comment 8•16 years ago
|
||
eh, first one wasn't quite right.
Attachment #334827 -
Attachment is obsolete: true
Attachment #334828 -
Flags: review?
Attachment #334827 -
Flags: review?
Comment 9•16 years ago
|
||
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?
Comment 10•16 years ago
|
||
Attachment #334835 -
Flags: review?(bienvenu)
Updated•16 years ago
|
Attachment #334835 -
Flags: review?(bienvenu) → review+
Updated•16 years ago
|
Assignee: justdave → bugmail
Component: MIME → Networking
Product: MailNews Core → Core
QA Contact: mime → networking
Version: unspecified → Trunk
Comment 11•16 years ago
|
||
biesi, are you the right person to review this for netwerk?
Comment 12•13 years ago
|
||
biesi, are you there?
Comment 13•13 years ago
|
||
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.
Comment 14•13 years ago
|
||
(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
Comment 15•13 years ago
|
||
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.
Comment 16•13 years ago
|
||
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.
Comment 17•13 years ago
|
||
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 18•13 years ago
|
||
Comment on attachment 334833 [details] [diff] [review]
Patch v3
Review of attachment 334833 [details] [diff] [review]:
-----------------------------------------------------------------
Attachment #334833 -
Flags: review?(cbiesinger) → review+
Comment 19•9 years ago
|
||
Updated•9 years ago
|
Whiteboard: [necko-active]
Comment 20•9 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/d4fe24eab2b74d044332321e23ba55dab8fdc687
Bug 345580 - Problem decoding quoted-printable question mark in subject r=biesi
Comment 21•9 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 9 years ago
status-firefox47:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla47
You need to log in
before you can comment on or make changes to this bug.
Description
•