Summary | Character encoding bug in cache behaviour |
Queue | Horde Base |
Queue Version | 3.0.4 |
Type | Bug |
State | Not A Bug |
Priority | 3. High |
Owners | slusarz (at) horde (dot) org |
Requester | michael (at) rollis (dot) chh |
Created | 04/12/2005 (7429 days ago) |
Due | |
Updated | 04/14/2005 (7427 days ago) |
Assigned | |
Resolved | 04/14/2005 (7427 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
State ⇒ Not A Bug
bug 1410. If you have anything new to add, please enter acomment there.
State ⇒ Unconfirmed
Priority ⇒ 3. High
Type ⇒ Bug
Summary ⇒ Character encoding bug in cache behaviour
Queue ⇒ Horde Base
After login when I open an Email with german umlauts from my inbox,
imp shows the mail correct.
Returning to the inbox and reopening the same mail again the umlauts
are suddenly corrupt. A ü becomes messed up to ü
BTW the email has correct mail header entries as follow:
Content-type: text/plain;
charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
I grepped through the session files (and session data in DB if turned
on) for a mail part and found, that the Mail is saved as ISO-8859-1
with decoded quoted printable and correct umlauts in the session.
So it looks like horde does something wrong on deserializing the
session object. Maybe it's getting the content as utf-8 instead of
ISO-8859-1.
Regards
Michael