I am sorry, I did not understand you correctly. And I also have to
revise my understanding of the matter.
RFC2616, Section 2.2 says:
The TEXT rule is only used for descriptive field contents and values
that are not intended to be interpreted by the message parser. Words
of *TEXT MAY contain
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Your tests show that IE6 correctly retrieves a UTF-8 encoded header?
Then it should wrongly decode the ISO-8859-1 equivalent value in the
X-JSON-UCS header as either C3 9F or DF can be ß, but not both, no?
When I said UCS encoded, I really meant
