…r before serialization. 3.3.3. Strings Strings are zero or more printable ASCII RFC0020 characters (i.e., the range %x20 to %x7E). Note that this excludes tabs, newlines, carriage returns, etc. Non-ASCII characters are not directly supported in Strings because they cause a number…

… before serialization. 3.3.3. Strings Strings are zero or more printable ASCII [RFC0020] characters (i.e., the range %x20 to %x7E). Note that this excludes tabs, newlines, carriage returns, etc. The ABNF for Strings is: sf-string = DQUOTE *chr DQUOTE chr = unescaped / escaped une…

…r before serialization. 3.3.3. Strings Strings are zero or more printable ASCII RFC0020 characters (i.e., the range %x20 to %x7E). Note that this excludes tabs, newlines, carriage returns, etc. The ABNF for Strings is: sf-string = DQUOTE *chr DQUOTE chr = unescaped / escaped unes…

… before serialization. 3.3.3. Strings Strings are zero or more printable ASCII [RFC0020] characters (i.e., the range %x20 to %x7E). Note that this excludes tabs, newlines, carriage returns, etc. Non-ASCII characters are not directly supported in Strings because they cause a numbe…

…Since the first two characters of a JSON text will always be ASCII characters [ RFC0020 ], it is possible to determine whether an octet stream is UTF-8, UTF-16 (BE or LE), or UTF-32 (BE or LE) by looking at the pattern of nulls in the first four octets. 00 00 00 xx UTF-32BE 00 xx…

…Since the first two characters of a JSON text will always be ASCII characters [ RFC0020 ], it is possible to determine whether an octet stream is UTF-8, UTF-16 (BE or LE), or UTF-32 (BE or LE) by looking at the pattern of nulls in the first four octets. 00 00 00 xx UTF-32BE 00 xx…

…Since the first two characters of a JSON text will always be ASCII characters [ RFC0020 ], it is possible to determine whether an octet stream is UTF-8, UTF-16 (BE or LE), or UTF-32 (BE or LE) by looking at the pattern of nulls in the first four octets. 00 00 00 xx UTF-32BE 00 xx…

…using Base64 ( [RFC4648], Section 4 ) into a sequence of US-ASCII characters ([ RFC0020 ]). The original definition of this authentication scheme failed to specify the character encoding scheme used to convert the user-pass into an octet sequence. In practice, most implementation…

…using Base64 ( [RFC4648], Section 4 ) into a sequence of US-ASCII characters ([ RFC0020 ]). The original definition of this authentication scheme failed to specify the character encoding scheme used to convert the user-pass into an octet sequence. In practice, most implementation…

…e resolution defined by [RFC3986]. At this stage, the URL is in ASCII encoding [RFC0020], even though the decoded components will be interpreted in UTF-8 [RFC3629] after steps 5, 8, and 9. NOTE: It doesn't matter what it is resolved relative to, since we already know it is an abs…

…using Base64 ( [RFC4648], Section 4 ) into a sequence of US-ASCII characters ([ RFC0020 ]). The original definition of this authentication scheme failed to specify the character encoding scheme used to convert the user-pass into an octet sequence. In practice, most implementation…

… Since the first two characters of a JSON text will always be ASCII characters [RFC0020], it is possible to determine whether an octet stream is UTF-8, UTF-16 (BE or LE), or UTF-32 (BE or LE) by looking at the pattern of nulls in the first four octets. 00 00 00 xx UTF-32BE 00 xx …

… Since the first two characters of a JSON text will always be ASCII characters [RFC0020], it is possible to determine whether an octet stream is UTF-8, UTF-16 (BE or LE), or UTF-32 (BE or LE) by looking at the pattern of nulls in the first four octets. 00 00 00 xx UTF-32BE 00 xx …