If there are only two significant input octets (e.g., 'Ma'), or when the last input group contains only two octets, all 16 bits will be captured in the first three Base64 digits (18 bits) the two least significant bits of the last content-bearing 6-bit block will turn out to be zero, and discarded on decoding (along with the succeeding = padding character): Using those four decimal numbers as indices for the Base64 alphabet, the corresponding ASCII characters are TWFu. Those 8 octal digits can be split into pairs ( 23 26 05 56), and each pair can be converted to decimal to yield 19 22 05 46. For example, the hexadecimal representation of the 24 bits above is 4d616e. Such conversion is available for both advanced calculators and programming languages. Hexadecimal to octal transformation is useful to convert between binary and Base64. = padding characters might be added to make the last encoded block contain four Base64 characters. Groups of 6 bits (6 bits have a maximum of 2 6 = 64 different binary values) are converted into individual numbers from start to end (in this case, there are four numbers in a 24-bit string), which are then converted into their corresponding Base64 character values.Īs this example illustrates, Base64 encoding converts three octets into four encoded characters. These three values are joined together into a 24-bit string, producing 010011010110000101101110. Encoded in ASCII, the characters M, a, and n are stored as the byte values 77, 97, and 110, which are the 8-bit binary values 01001101, 01100001, and 01101110. In the above quote, the encoded value of Man is TWFu. Here is a well-known idiom from distributed computing: The more typical use is to encode binary data (such as an image) the resulting Base64 data will only contain 64 different ASCII characters, all of which can reliably be transferred across systems that may corrupt the raw source bytes. The example below uses ASCII text for simplicity, but this is not a typical use case, as it can already be safely transferred across all systems that can handle Base64. This is the Base64 alphabet defined in RFC 4648 §4. For instance, uuencode uses uppercase letters, digits, and many punctuation characters, but no lowercase. The earliest instances of this type of encoding were created for dial-up communication between systems running the same OS, for example, uuencode for UNIX and BinHex for the TRS-80 (later adapted for the Macintosh), and could therefore make more assumptions about what characters were safe to use. Other variations share this property but differ in the symbols chosen for the last two values an example is UTF-7. For example, MIME's Base64 implementation uses A– Z, a– z, and 0– 9 for the first 62 values. This combination leaves the data unlikely to be modified in transit through information systems, such as email, that were traditionally not 8-bit clean. The general strategy is to choose 64 characters that are common to most encodings and that are also printable. Which characters are chosen to represent the 64 values varies between implementations.
Each Base64 digit can take on 64 different values, encoding 6 bits of data.
0 kommentar(er)
