About: 72500 results

RFC 4648 - The Base16, Base32, and Base64 Data ... - IETF Tools
https://tools.ietf.org/html/rfc4648
The Base16, Base32, and Base64 Data Encodings. Status of This Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to ...
RFC 3548 - The Base16, Base32, and Base64 Data Encodings
https://tools.ietf.org/html/rfc3548
MIME [3] is often used as a reference for base64 without considering the consequences for line-wrapping or non-alphabet characters. The purpose of this specification is to establish common alphabet and encoding considerations. This will ...
RFC 2397 - The "data" URL scheme - IETF Tools
https://tools.ietf.org/html/rfc2397
The appearance of ";base64" means that the data is encoded as base64. Without ";base64", the data (as a sequence of octets) is represented using ASCII encoding for octets inside the range of safe URL characters and using the standard %xx ...
RFC 3548 - IETF Tools
https://tools.ietf.org/rfc/rfc3548.txt
Abstract This document describes the commonly used base 64, base 32, and base 16 encoding schemes. It also discusses the ... 13 Josefsson Informational [ Page 1] RFC 3548 The Base16, Base32, and Base64 Data Encodings July 2003 1.
RFC 4648 - IETF Tools
https://tools.ietf.org/rfc/rfc4648
The base64 and base32 alphabets use padding, as described below in sections 4 and 6, but the base16 alphabet does ... RFC 4648 Base-N Encodings October 2006 Table 2: The "URL and Filename safe" Base 64 Alphabet Value Encoding ...
Base64 - ウィキペディア
https://ja.wikipedia.org/wiki/Base64
Base64は、データを64種類の印字可能な英数字のみを用いて、それ以外の文字を扱う ことの出来ない通信環境にてマルチバイト文字やバイナリデータを ... (可変), 76, CR+ LF, 許可 (破棄される), (なし). RFC 3548 や RFC 4648 の標準の 'Base64' エンコーディング, +, /, = (必須), はい (最終行を除く), 64 または 76 (改行が必要な場合 のみ), CR+LF (改行が必要な場合のみ), 禁止, (なし). OpenPGP用「Radix-64」
Base64 - Wikipedia
https://en.wikipedia.org/wiki/Base64
MIME's Base64 encoding is based on that of the RFC 1421 version of PEM: it uses the same 64-character alphabet and encoding mechanism as PEM, and uses the = symbol for output padding in the same way, as ...
RFC 4648 - IETF
https://www.ietf.org/rfc/rfc4648.txt
This encoding may be referred to as "base64". The Base 64 encoding is designed to represent arbitrary sequences of octets in a form that allows the use of both upper- and lowercase letters but that need not ...
RFC 2045 - IETF
https://www.ietf.org/rfc/rfc2045.txt
Examples of such encodings currently used in the Internet include pure hexadecimal, uuencode, the 3-in-4 base 64 scheme specified in RFC 1421, the Andrew Toolkit Representation [ATK], and many others. The limitations of RFC 822 mail ...
RFC 4648 - The Base16, Base32, and Base64 ... - IETF Datatracker
https://datatracker.ietf.org/doc/rfc4648
The Base16, Base32, and Base64 Data Encodings (RFC 4648, October 2006) ... Abstract This document describes the commonly used base 64, base 32, and base 16 encoding schemes. It also discusses the use of line-feeds in encoded data ...