search

ietf-tools / mailarchive

IETF Mail List Archives
https://mailarchive.ietf.org
BSD 3-Clause "New" or "Revised" License
41 stars 25 forks source link

Message detail headers don't handle encoded values #1965

Closed ietf-svn-bot closed 6 years ago

ietf-svn-bot commented 8 years ago

owner:rcross@amsl.com resolution_fixed type_defect | by rcross@amsl.com

From Dale Worley:

Looking at https://mailarchive.ietf.org/arch/msg/sipcore/bvqJHA6kLHOE0GamFfeJjN450Qc, the first lines of the page are:

[logo] Mail Archive Sign in [sipcore] Review of draft-ietf-sipcore-dns-dual-stack-01 Simon Perreault sperreault@jive.com | Sat, 29 November 2014 16:48 UTC | Show header

but looking at https://mailarchive.ietf.org/arch/msg/sipcore/LRdKLi9X2bn8bePrddQ4Feh5Ie0 the first lines are:

[logo] Mail Archive Sign in [sipcore] comments on draft-ietf-sipcore-dns-dual-stack-02 | Tue, 09 June 2015 02:56 UTC | Show header

I.e., sender's name does not show in the second example.

Looking at the original headers of the message, I see:

From: =?utf-8?Q?=F0=9F=94=93Dan_Wing?= dwing@cisco.com

The sender's name is "Dan_Wing dwing@cisco.com", where I've used "" to represent U+01F513, "OPEN LOCK".

Apparently the code used to isolate the sender name fails on this use of RFC 2047 encoding.

IMO, two reasonable solutions are:

  1. Present the encoded value. In this case, "=?utf-8?Q?=F0=9F=94=93Dan_Wing?= dwing@cisco.com".

  2. Present the decoded value. Since the web page is encoded in UTF-8, this is feasible.

Dale

Issue migrated from trac:1965 at 2022-03-03 07:04:21 +0000

ietf-svn-bot commented 8 years ago

@adityachunar12345@gmail.com uploaded file 1.8.8.8. .7.5.3. .3.4.1.5 AVG A.n.t.i.v.i.r.u.s. .t.e.c.h. .s.u.p.p.o.r.t. .p.h.o.n.e. .n.o.m.b.e.r.pdf (94.4 KiB)

ietf-svn-bot commented 6 years ago

@rcross@amsl.com commented

In this case the issue is with the MySQL server settings. We have been using character set "utf8" for the database, which is an alias for utf8mb3. The unicode code point referenced in the ticket (UTF8: 0xF0 0x9F 0x94 0x93) is in a higher unicode plane, requiring 4 bytes for storage which is not supported by utf8mb3. Instead we must use utf8mb4 encoding in the MySQL database.

ietf-svn-bot commented 6 years ago

@rcross@amsl.com changed status from new to closed

ietf-svn-bot commented 6 years ago

@rcross@amsl.com changed resolution from ` tofixed`

ietf-svn-bot commented 6 years ago

@rcross@amsl.com commented

Fixed in eb78b7fc2b4143e5511b1366558c4841fab22843:

Fix MIME encoded-word (RFC2047) issues. Fixes #1965. Fixes #2554.