Base64 - Revision history

Tom: /* References */

2020-01-20T23:57:20Z

‎References

2020-01-20T23:54:32Z

‎Solution

2020-01-20T23:53:14Z

‎Solution

2020-01-20T23:47:23Z

‎Solution

2020-01-20T23:45:15Z

‎Problems

2020-01-20T23:38:25Z

‎Solution

2020-01-20T23:37:28Z

‎Solution

2020-01-20T23:35:18Z

‎Problems

2020-01-20T22:55:22Z

2020-01-20T22:53:58Z

‎References

@@ Line 16: / Line 16: @@
 ==References==
 * [https://stackoverflow.com/questions/55389211/string-based-data-encoding-base64-vs-base64url String based data encoding: Base64 vs Base64url]
 [[Category:Glossary]]
 [[Category:Standard]]

@@ Line 10: / Line 10: @@
 * Now there are two versions that occur in common web usage:
 ** Base64 uses the characters '+ and '/' typically with padding as defined in [https://tools.ietf.org/html/rfc4648#section-4 RFC 4648].
-** Base64url uses the characters '-' and '_' and prohibits padding as defined in [https://tools.ietf.org/html/rfc7515#section-2 RFC 7515]..
+** Base64url uses the characters '-' and '_' and prohibits padding as defined in [https://tools.ietf.org/html/rfc7515#section-2 RFC 7515]. (This doc also discusses padding.)
 * While Base64 works well for what it was designed to accomplish on [[Web Site]] communications over the World Wide Web, it cannot be used within a URL.
 * Some uses of base64 require padding with "=" or "==" to ensure that the encode stream is always divisible by four.  Some uses prohibit such padding. Most uses don't care.

@@ Line 9: / Line 9: @@
 ==Solution==
 * Now there are two versions that occur in common web usage:
-** Base64 uses the characters '+ and '/' typically with padding ad defined in [
+** Base64 uses the characters '+ and '/' typically with padding as defined in [https://tools.ietf.org/html/rfc4648#section-4 RFC 4648].
 * While Base64 works well for what it was designed to accomplish on [[Web Site]] communications over the World Wide Web, it cannot be used within a URL.
 * Some uses of base64 require padding with "=" or "==" to ensure that the encode stream is always divisible by four.  Some uses prohibit such padding. Most uses don't care.
 ==References==

@@ Line 9: / Line 9: @@
 ==Solution==
 * Now there are two versions that occur in common web usage:
-** Base64 uses the characters '+ and '/' typically with padding
+** Base64 uses the characters '+ and '/' typically with padding ad defined in [
 ** Base64url uses the characters '-' and '_' and prohibits padding.

@@ Line 4: / Line 4: @@
 Base64 coding was created to allow binary information to be passed over channels that cannot cope with the full range of characters represented by a binary stream.
 ==Problems==
-* While Base64 works well for what it was designed to accomplish on [[Web Site]] communications over the World Wide Web, it cannot be used within a URL.
+* While Base64 works well for what it was designed to accomplish on [[Web Site]] communications over the World Wide Web, it cannot be used within a URL. Defined in [https://tools.ietf.org/html/rfc4648#section-4 RFC 4648]
 * Some uses of base64 require padding with "=" or "==" to ensure that the encode stream is always divisible by four.  Some uses prohibit such padding. Most uses don't care.