Base64 - Revision history

Jsummers at 16:52, 11 December 2015

2015-12-11T16:52:44Z

Dan Tobias at 00:45, 25 August 2014

2014-08-25T00:45:33Z

Dan Tobias: /* Utilities */

2014-08-24T23:49:30Z

‎Utilities

Dan Tobias: /* Programming libraries/modules */

2014-08-24T23:49:17Z

‎Programming libraries/modules

Jsummers: Change primary category to Transfer Encodings

2014-08-24T22:55:44Z

Change primary category to Transfer Encodings

Dan Tobias at 00:06, 8 April 2014

2014-04-08T00:06:27Z

Dan Tobias: /* Programming libraries/modules */

2014-01-24T02:00:02Z

‎Programming libraries/modules

Dan Tobias: /* References */

2014-01-24T01:54:21Z

‎References

Dan Tobias at 04:32, 12 December 2012

2012-12-12T04:32:51Z

Dan Tobias: /* References */

2012-12-11T05:03:57Z

‎References

@@ Line 1: / Line 1: @@
 {{FormatInfo
 |subcat=Transfer Encodings
 |image=Base64.png
@@ Line 24: / Line 25: @@
 * RFC 4648
-== Utilities ==
+== Software ==
 * [http://www.base64encode.org/ Base64 online encoder/decoder]
 * [http://search.cpan.org/~gaas/MIME-Base64-3.14/Base64.pm Base64 module for Perl]

@@ Line 1: / Line 1: @@
 {{FormatInfo
 |subcat=Transfer Encodings
 }}
 '''Base64''' is one of the two transfer encodings used in [[MIME]] e-mail messages to encode binary data entirely in characters of the 7-bit [[ASCII]] range so that it could be safely transmitted even through systems not supporting anything else (which was more of an issue in the 1970s when e-mail protocols were defined than at present). The other encoding is [[Quoted-printable]], which is best suited for data that is mostly ASCII text but may have a few "unsafe" characters needing encoding. Base64 is best suited for binary data where all byte values from 0 to 255 are likely to occur, and encodes them efficiently (but not easily readably by the "naked eye").

@@ Line 24: / Line 24: @@
 == Utilities ==
-* [http://www.base64encode.org/ Base 64 online encoder/decoder]
+* [http://www.base64encode.org/ Base64 online encoder/decoder]
 == Programming libraries/modules ==

@@ Line 22: / Line 22: @@
 * RFC 3548
 * RFC 4648
 == Programming libraries/modules ==

@@ Line 1: / Line 1: @@
 {{FormatInfo
-|subcat=E-Mail, newsgroups, and forums
+|subcat=Transfer Encodings
 }}
 '''Base64''' is one of the two transfer encodings used in [[MIME]] e-mail messages to encode binary data entirely in characters of the 7-bit [[ASCII]] range so that it could be safely transmitted even through systems not supporting anything else (which was more of an issue in the 1970s when e-mail protocols were defined than at present). The other encoding is [[Quoted-printable]], which is best suited for data that is mostly ASCII text but may have a few "unsafe" characters needing encoding. Base64 is best suited for binary data where all byte values from 0 to 255 are likely to occur, and encodes them efficiently (but not easily readably by the "naked eye").
-'''Base64''' is one of the two transfer encodings used in [[Mime-type|MIME]] e-mail messages to encode binary data entirely in characters of the 7-bit [[ASCII]] range so that it could be safely transmitted even through systems not supporting anything else (which was more of an issue in the 1970s when e-mail protocols were defined than at present). The other encoding is [[Quoted-printable]], which is best suited for data that is mostly ASCII text but may have a few "unsafe" characters needing encoding. Base64 is best suited for binary data where all byte values from 0 to 255 are likely to occur, and encodes them efficiently (but not easily readably by the "naked eye").
 A Base64-encoded message part is indicated in its MIME headers (following the '''Content-type''' header giving the type of data) with the line:
@@ Line 30: / Line 29: @@
 * [[Wikipedia:MIME#Content-Transfer-Encoding|Content Transfer Encoding (Wikipedia)]]
 * [[Wikipedia:Base64|Base64 (Wikipedia)]]

@@ Line 16: / Line 16: @@
 * The characters + and /
-A base-64 digit (fitting in one byte of the encoded data) encodes six bits of the original data. Since a byte has eight bits, three bytes of the original file (24 bits) correspond to four base-64 digits. Thus, the encoding method requires you to consider each group of three bytes as a number (big-endian), and express it as four digits in the base-64 system. The padding character = is used to fill out a group of four characters if not needed to encode the end of the original data.
+A base-64 digit (fitting in one byte of the encoded data) encodes six bits of the original data. Since a byte has eight bits, three bytes of the original file (24 bits) correspond to four base-64 digits. Thus, the encoding method requires you to consider each group of three bytes as a number ([[Endianness|big-endian]]), and express it as four digits in the base-64 system. The padding character = is used to fill out a group of four characters if not needed to encode the end of the original data.
 [[BinHex]] uses a similar encoding scheme (except for really early versions which used hexadecimal as implied by the name), but with a different set of 64 characters and some other format differences.
@@ Line 28: / Line 28: @@
 == Other links ==
-* [http://en.wikipedia.org/wiki/MIME#Content-Transfer-Encoding Content Transfer Encoding (Wikipedia)]
+* [[Wikipedia:MIME#Content-Transfer-Encoding|Content Transfer Encoding (Wikipedia)]]
-* [http://en.wikipedia.org/wiki/Base64 Base64 (Wikipedia)]
+* [[Wikipedia:Base64|Base64 (Wikipedia)]]