-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: Agents-4.0.1, 13.0.0
-
Fix Version/s: Agents-4.1.0, Agents-5.0
-
Component/s: documentation, web agents
-
Sprint:Sprint 115 Team Shakespeare
-
Epic Link:
-
Support Ticket IDs:
-
Verified Version/s:
According to RFC 2616 Section 4.2
The content of a header field may only be "the OCTETs making up the field-value and consisting of either *TEXT or combinations of token, separators, and quoted-string" and in section 2.1 makes explicit that "Words of *TEXT MAY contain characters from character sets other than ISO-8859-1 [22] only when encoded according to the rules of RFC 2047 [14]."
For illustration purpose, we use a fictional name Hunter Poe Программное обеспечение воин
In the OpenAM agents if the raw bytes are consumed and displayed, it is
Hunter Poe ��ог�аммное обе�пе�ение воин
Although if the raw bytes is consumed as ASCII and then convert them UTF-8 it displays correctly as
Hunter Poe Программное обеспечение воин
But according to RFC 2047 it should be displayed like this:
=?UTF-8?B?SHVudGVyIFBvZSDQn9GA0L7Qs9GA0LDQvNC80L3QvtC1INC+0LHQtdGB0L/QtdGH0LXQvdC40LUg0LLQvtC40L0=?=
- is related to
-
AMAGENTS-543 Some valid special characters set as HTTP_HEADERs are not being encoded
-
- Resolved
-