Uploaded image for project: 'OpenAM'
  1. OpenAM
  2. OPENAM-8904

OpenAM did not follow RFC 2616 and RFC 2047

    Details

    • Support Ticket IDs:

      Description

      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=?=
      

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                chris.lee Chris Lee
                Reporter:
                sam.phua Sam Phua
                QA Assignee:
                edwardb
              • Votes:
                1 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: