View source for UTF-7

{{Short description|Character encoding}}
{{Use dmy dates|date=June 2020}}
{{Infobox character encoding
| name = UTF-7
| image = 
| mime = 
| alias = 
| standard = {{IETF RFC|2152}}
| lang = International
<!-- Not | extends = [[ASCII]] as even plain ASCII text can be reinterpreted. -->
| encodes = [[ISO/IEC 10646]] ([[Unicode]])
| status = 
| prev = [[HZ-GB-2312]]
| next = [[UTF-8]] over [[8BITMIME]]
| classification = [[Unicode Transformation Format]], [[ASCII armor]], [[variable-width encoding]], [[state (computer science)|stateful encoding]]
}}
'''UTF-7''' (7-[[bit]] [[Unicode Transformation Format]]) is an obsolete variable-length character encoding for representing [[Unicode]] text using a stream of [[ASCII]] characters. It was originally intended to provide a means of encoding [[Unicode]] text for use in [[Internet]] [[E-mail]] messages that was more efficient than the combination of [[UTF-8]] with [[quoted-printable]].

UTF-7 (according to its RFC) isn't a "[[Unicode Transformation Format]]", as the definition can only encode code points in the [[Basic Multilingual Plane|BMP]] (the first 65536 Unicode code points, which does not include [[emojis]] and many other characters). However if a UTF-7 translator is to/from [[UTF-16]] then it can (and probably does){{citation needed|date=August 2023}} encode each surrogate half as though it was a 16-bit code point, and thus can encode all code points. It is unclear if other UTF-7 software (such as translators to UTF-32 or UTF-8) support this.

UTF-7 has never been an official standard of the [[Unicode Consortium]]. It is known to have security issues, which is why software has been changed to disable its use.<ref name="dotnet5"/> It is prohibited in [[HTML 5]].<ref>{{Cite web |url=https://www.w3.org/TR/html51/syntax.html#character-encodings |title=8.2.2.3. Character encodings |website=HTML 5.1 Standard |publisher=W3C}}</ref><ref>{{Cite web |url=https://html.spec.whatwg.org/multipage/parsing.html#character-encodings |title=12.2.3.3 Character encodings |website=HTML Living Standard |publisher=WHATWG}}</ref>

==Motivation==
[[MIME]], the modern standard for e-mail formats, forbids encoding of [[header (computing)|headers]] using byte values above the ASCII range. Although MIME allows encoding the message body in various [[character set]]s (broader than ASCII), the underlying transmission infrastructure ([[Simple Mail Transfer Protocol|SMTP]], the main E-mail transfer standard) is still not guaranteed to be [[8-bit clean]]. Therefore, a non-trivial content transfer encoding has to be applied in case of doubt. Unfortunately, [[Base64]] has a disadvantage of making even [[ASCII]] characters unreadable in non-MIME clients. On the other hand, UTF-8 combined with [[quoted-printable]] produces a very size-inefficient format requiring 6&ndash;9 bytes for non-ASCII characters from the [[Basic Multilingual Plane|BMP]] and 12 bytes for characters outside the BMP.

Provided certain rules are followed during encoding, UTF-7 can be sent in e-mail without using an underlying MIME [[MIME#Content-Transfer-Encoding|transfer encoding]], but still must be explicitly identified as the text character set. In addition, if used within e-mail headers such as "Subject:", UTF-7 must be contained in MIME [[MIME#Encoded-Word|encoded word]]s identifying the character set. Since encoded words force use of either [[quoted-printable]] or [[Base64]], UTF-7 was designed to avoid using the = sign as an escape character to avoid double escaping when it is combined with quoted-printable (or its variant, the RFC 2047/1522 "Q"-encoding of headers).

UTF-7 is generally not used as a native representation within applications as it is very awkward to process.  Despite its size advantage over the combination of UTF-8 with either quoted-printable or Base64, the now defunct [[Internet Mail Consortium]] recommended against its use.<ref>{{Cite web|url=https://www.imc.org/imcr-010.html|title=Using International Characters in Internet Mail |work=Internet Mail Consortium |date=1 August 1998 |archive-url=https://web.archive.org/web/20150907234243/https://www.imc.org/imcr-010.html |archive-date=2015-09-07}}</ref>

[[8BITMIME]] has also been introduced, which reduces the need to encode message bodies in a 7-bit format.

A modified form of UTF-7 (sometimes dubbed 'mUTF-7'<ref>{{cite web
| url          = https://doc.dovecot.org/configuration_manual/mail_location/
| title        = Configuration Manual
| at           = Sec. "Mail Location Settings"
| author       = <!--Not stated--> 
| date         = 8 February 2023
| website      = Dovecot Documentation
| access-date  = 2023-02-28
| quote        = Store mailbox names on disk using UTF-8 instead of modified UTF-7 (mUTF-7).
}}</ref>) was used in the [[Internet Message Access Protocol|Internet Message Access Protocol (IMAP)]] e-mail retrieval protocol, version 4 rev 1, for "international" mailbox names.{{Ref RFC|3501|section=5.1.3 "Mailbox International Naming Convention"
 |quote=In modified UTF-7, printable [[US-ASCII]] characters, except for "&", represent themselves….  The character "&" (0x26) is represented by the two-octet sequence "&-". All other characters… are represented in modified BASE64….
}} 
The following version, IMAP version 4 rev 2, uses UTF-8 instead.{{Ref RFC|9051|section=5.1. "Mailbox Naming" |quote=In IMAP4rev2, mailbox names are encoded in Net-Unicode (this differs from IMAP4rev1).}}

==Description==
UTF-7 was first proposed as an experimental protocol in RFC 1642, ''A Mail-Safe Transformation Format of Unicode''.  This [[Request for Comments|RFC]] has been made obsolete by RFC 2152, an informational RFC which never became a standard. As RFC 2152 clearly states, the RFC "does not specify an Internet standard of any kind". Despite this, RFC 2152 is quoted as the definition of UTF-7 in the IANA's list of charsets. Neither is UTF-7 a Unicode Standard.  ''The Unicode Standard 5.0'' only lists UTF-8, UTF-16 and UTF-32.
There is also a modified version, specified in RFC 2060, which is sometimes identified as UTF-7.

Some characters can be represented directly as single ASCII bytes. The first group is known as "direct characters" and contains 62 alphanumeric characters and 9 symbols: <code>' ( ) , - . / : ?</code>. The direct characters are safe to include literally. The other main group, known as "optional direct characters", contains all other printable characters in the range {{U+|0020}}&ndash;U+007E except <code>~ \ +</code> and space (the characters {{code|\}} and {{code|~}} being excluded due to being redefined in "variants of ASCII" such as [[JIS-Roman]]). Using the optional direct characters reduces size and enhances human readability but also increases the chance of breakage by things like badly designed mail gateways and may require extra escaping when used in encoded words for header fields.

Space, tab, carriage return and line feed may also be represented directly as single ASCII bytes. However, if the encoded text is to be used in e-mail, care is needed to ensure that these characters are used in ways that do not require further content transfer encoding to be suitable for e-mail. The plus sign (<code>+</code>) ''may'' be encoded as <code>+-</code>.

Other characters must be encoded in [[UTF-16]] (hence U+10000 and higher would be encoded into two surrogates), and then in [[Base64#UTF-7|modified Base64]]. The start of these blocks of modified Base64-encoded UTF-16 is indicated by a <code>+</code> sign. The end is indicated by any character not in the modified Base64 set. If the character after the modified Base64 is a <code>-</code> (ASCII [[hyphen-minus]]) then it is consumed by the decoder and decoding resumes with the next character. Otherwise decoding resumes with the character after the Base64.

==Examples==
* "<code>Hello, World!</code>" is encoded as "<code>Hello, World+ACE-</code>"
* "<code>1 + 1 = 2</code>" is encoded as "<code>1 +- 1 +AD0- 2</code>"
* "<code>£1</code>" is encoded as "<code>+AKM-1</code>". The Unicode code point for the [[pound sign]] is U+00A3 which converts into [[modified Base64]] as in the table below. There are two bits left over, which are padded to 0.
{| class="wikitable"
 ! Hex digit
 | colspan="4" align="center"| 0
 | colspan="4" align="center"| 0
 | colspan="4" align="center"| A
 | colspan="4" align="center"| 3
 | colspan="2" | &nbsp;
 |-
 ! Bit pattern 
 |0||0||0||0||0||0||0||0||1||0||1||0||0||0||1||1||0||0
 |-
 ! Index
 | colspan="6" align="center"| 0
 | colspan="6" align="center"| 10
 | colspan="6" align="center"| 12
 |-
 ! Base64-Encoded
 | colspan="6" align="center"| A
 | colspan="6" align="center"| K
 | colspan="6" align="center"| M
 |}

==Algorithm for encoding and decoding==

===Encoding===
First, an encoder must decide which characters to represent directly in ASCII form, which <code>+</code> have to be escaped as <code>+-</code>, and which to place in blocks of Unicode characters. The expansion cost of UTF-7 can be high: for example, the character sequence U+10FFFF U+0077 U+10FFFF is 9 bytes in UTF-8, but 17 bytes in UTF-7. (At worst, treating every codepoint as a sequence in its own right produces the maximum expansion of 5x, e.g. when encoding <code>@@</code> as <code>+AEA-+AEA-</code>.) Each Unicode sequence must be encoded using the following procedure, then surrounded by the appropriate delimiters.

Using the £† (U+00A3 U+2020) character sequence as an example:

{{ordered list
|1= Express the character's Unicode numbers (UTF-16) in binary:{{unbulleted list
|<samp>0x00A3 → 0000 0000 1010 0011</samp>
|<samp>0x2020 → 0010 0000 0010 0000</samp>}}
|2= Concatenate the binary sequences:<br />
<samp>0000 0000 1010 0011 and 0010 0000 0010 0000 → 0000 0000 1010 0011 0010 0000 0010 0000</samp>
|3= Regroup the binary into groups of six bits, starting from the left:<br />
<samp>0000 0000 1010 0011 0010 0000 0010 0000 → 000000 001010 001100 100000 001000 00</samp>
|4= If the last group has fewer than six bits, add trailing zeros:<br />
<samp>000000 001010 001100 100000 001000 00 → 000000 001010 001100 100000 001000 000000</samp>
|5= Replace each group of six bits with a respective Base64 code:<br />
<samp>000000 001010 001100 100000 001000 000000 → AKMgIA</samp>
}}

===Decoding===
First an encoded data must be separated into plain ASCII text chunks (including '''+'''es followed by a dash) and nonempty Unicode blocks as mentioned in the description section. Once this is done, each Unicode block must be decoded with the following procedure (using the result of the encoding example above as our example)

#Express each Base64 code as the bit sequence it represents:<br /><samp>AKMgIA → 000000 001010 001100 100000 001000 000000</samp>
#Regroup the binary into groups of sixteen bits, starting from the left:<br /><samp>000000 001010 001100 100000 001000 000000 → 0000000010100011 0010000000100000 0000</samp>
#If there is an incomplete group at the end containing only zeros, discard it (if the incomplete group contains any ones, the code is invalid):<br /><samp>0000000010100011 0010000000100000</samp>
#Each group of 16 bits is a character's Unicode (UTF-16) number and can be expressed in other forms:<br /><samp>0000 0000 1010 0011 ≡ 0x00A3 ≡ 163<sub>10</sub></samp>

==Byte order mark==
A byte order mark (BOM) is an optional special byte sequence at the very start of a stream or file that, without being data itself, indicates the encoding used for the data that follows; it can be used<!--it often isn't--> in the absence of metadata that denotes the encoding. For a given encoding scheme, it's that scheme's representation of Unicode code point <code>U+FEFF</code>.<ref>{{Cite web|url=https://unicode.org/faq/utf_bom.html|title=FAQ – UTF-8, UTF-16, UTF-32 & BOM}}</ref>

While it's typically a single, fixed byte sequence, in UTF-7 four variations may appear, because the last 2 bits of the 4th byte of the UTF-7 encoding of <code>U+FEFF</code> belong to the ''following'' character, resulting in 4 possible bit patterns and therefore 4 different possible bytes in the 4th position. See the UTF-7 entry in the [[Byte order mark#Byte order marks by encoding|table of Unicode byte order marks]].<ref>{{cite web| url=https://unicode.org/L2/L2021/21038-bom-guidance.pdf | title=Clarify guidance for use of a BOM as a UTF-8 encoding signature | access-date=2024-01-17}}</ref>

==Security==
UTF-7 allows multiple representations of the same source string. In particular, ASCII characters can be represented as part of Unicode blocks. As such, if standard ASCII-based escaping or validation processes are used on strings that may be later interpreted as UTF-7, then Unicode blocks may be used to slip malicious strings past them. To mitigate this problem, systems should perform decoding before validation and should avoid attempting to autodetect UTF-7.

Older versions of [[Internet Explorer]] can be tricked into interpreting the page as UTF-7. This can be used for a [[cross-site scripting]] attack as the <code>&lt;</code> and <code>&gt;</code> marks can be encoded as <code>+ADw-</code> and <code>+AD4-</code> in UTF-7, which most validators let through as simple text.<ref>{{cite web|url=https://code.google.com/p/doctype-mirror/wiki/ArticleUtf7 |title=ArticleUtf7 - doctype-mirror - UTF-7: the case of the missing charset - Mirror of Google Doctype - Google Project Hosting |date=2011-10-14 |access-date=2012-06-29}}</ref>

UTF-7 is considered obsolete, at least for Microsoft software (.NET), with code paths previously supporting it intentionally broken (to prevent security issues) in .NET 5, in 2020.<ref name="dotnet5">{{Cite web|title=Breaking change: UTF-7 code paths are obsolete|url=https://docs.microsoft.com/en-us/dotnet/core/compatibility/core-libraries/5.0/utf-7-code-paths-obsolete|access-date=2021-01-08|website=docs.microsoft.com|language=en-us}}</ref>

==See also==
* [[Comparison of Unicode encodings]]

==References==
{{reflist}}

{{Unicode navigation}}
{{Character encoding}}

{{DEFAULTSORT:Utf-07}}
[[Category:Character encoding]]
[[Category:Unicode Transformation Formats]]