Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
cpython
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
cpython
Commits
ad9aaeea
Commit
ad9aaeea
authored
Jan 04, 2004
by
Barry Warsaw
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Documentation for new RFC 3548 functions.
parent
30ff12ff
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
106 additions
and
13 deletions
+106
-13
Doc/lib/libbase64.tex
Doc/lib/libbase64.tex
+106
-13
No files found.
Doc/lib/libbase64.tex
View file @
ad9aaeea
\section
{
\module
{
base64
}
---
\section
{
\module
{
base64
}
---
Encode and decode MIME base64 data
}
RFC 3548: Base16, Base32, Base64 Data Encodings
}
\declaremodule
{
standard
}{
base64
}
\declaremodule
{
standard
}{
base64
}
\modulesynopsis
{
Encode and decode files using the MIME base64 data.
}
\modulesynopsis
{
RFC 3548: Base16, Base32, Base64 Data Encodings
}
\indexii
{
base64
}{
encoding
}
\indexii
{
base64
}{
encoding
}
\index
{
MIME!base64 encoding
}
\index
{
MIME!base64 encoding
}
This module performs base64 encoding and decoding of arbitrary binary
This module provides data encoding and decoding as specified in
strings into text strings that can be safely sent by email or included
\rfc
{
3548
}
. This standard defines the Base16, Base32, and Base64
as part of an HTTP POST request. The
algorithms for encoding and decoding arbitrary binary strings into
encoding scheme is defined in
\rfc
{
1521
}
(
\emph
{
MIME
text strings that can be safely sent by email, used as parts of URLs,
(Multipurpose Internet Mail Extensions) Part One: Mechanisms for
or included as part of an HTTP POST request. The encoding algorith is
Specifying and Describing the Format of Internet Message Bodies
}
,
not the same as the
\program
{
uuencode
}
program.
section 5.2, ``Base64 Content-Transfer-Encoding'') and is used for
MIME email and various other Internet-related applications; it is not
the same as the output produced by the
\program
{
uuencode
}
program.
For example, the string
\code
{
'www.python.org'
}
is encoded as the
string
\code
{
'd3d3LnB5dGhvbi5vcmc=
\e
n'
}
.
There are two interfaces provided by this module. The modern
interface supports encoding and decoding string objects using all
three alphabets. The legacy interface provides for encoding and
decoding to and from file-like objects as well as strings, but only
using the Base64 standard alphabet.
The modern interface provides:
\begin{funcdesc}
{
b64encode
}{
s
\optional
{
, altchars
}}
Encode a string use Base64.
\var
{
s
}
is the string to encode. Optional
\var
{
altchars
}
must be a
string of at least length 2 (additional characters are ignored) which
specifies an alternative alphabet for the
\code
{
+
}
and
\code
{
/
}
characters. This allows an application to e.g. generate URL or
filesystem safe Base64 strings. The default is
\code
{
None
}
, for which
the standard Base64 alphabet is used.
The encoded string is returned.
\end{funcdesc}
\begin{funcdesc}
{
b64decode
}{
s
\optional
{
, altchars
}}
Decode a Base64 encoded string.
\var
{
s
}
is the string to decode. Optional
\var
{
altchars
}
must be a
string of at least length 2 (additional characters are ignored) which
specifies the alternative alphabet used instead of the
\code
{
+
}
and
\code
{
/
}
characters.
The decoded string is returned. A
\exception
{
TypeError
}
is raised if
\var
{
s
}
were incorrectly padded or if there are non-alphabet
characters present in the string.
\end{funcdesc}
\begin{funcdesc}
{
standard
_
b64encode
}{
s
}
Encode string
\var
{
s
}
using the standard Base64 alphabet.
\end{funcdesc}
\begin{funcdesc}
{
standard
_
b64decode
}{
s
}
Decode string
\var
{
s
}
using the standard Base64 alphabet.
\end{funcdesc}
\begin{funcdesc}
{
urlsafe
_
b64encode
}{
s
}
Encode string
\var
{
s
}
using a URL-safe alphabet, which substitutes
\code
{
-
}
instead of
\code
{
+
}
and
\code
{_}
instead of
\code
{
/
}
in the
standard Base64 alphabet.
\end{funcdesc}
\begin{funcdesc}
{
urlsafe
_
b64decode
}{
s
}
Decode string
\var
{
s
}
using a URL-safe alphabet, which substitutes
\code
{
-
}
instead of
\code
{
+
}
and
\code
{_}
instead of
\code
{
/
}
in the
standard Base64 alphabet.
\end{funcdesc}
\begin{funcdesc}
{
b32encode
}{
s
}
Encode a string using Base32.
\var
{
s
}
is the string to encode. The
encoded string is returned.
\end{funcdesc}
\begin{funcdesc}
{
b32decode
}{
s
\optional
{
, casefold
\optional
{
, map01
}}}
Decode a Base32 encoded string.
\var
{
s
}
is the string to decode. Optional
\var
{
casefold
}
is a flag
specifying whether a lowercase alphabet is acceptable as input. For
security purposes, the default is
\code
{
False
}
.
\rfc
{
3548
}
allows for optional mapping of the digit 0 (zero) to the
letter O (oh), and for optional mapping of the digit 1 (one) to either
the letter I (eye) or letter L (el). The optional argument
\var
{
map01
}
when not
\code
{
None
}
, specifies which letter the digit 1 should
be mapped to (when map01 is not
\var
{
None
}
, the digit 0 is always
mapped to the letter O). For security purposes the default is
\code
{
None
}
, so that 0 and 1 are not allowed in the input.
The decoded string is returned. A
\exception
{
TypeError
}
is raised if
\var
{
s
}
were incorrectly padded or if there are non-alphabet characters
present in the string.
\end{funcdesc}
\begin{funcdesc}
{
b16encode
}{
s
}
Encode a string using Base16.
\var
{
s
}
is the string to encode. The encoded string is returned.
\end{funcdesc}
\begin{funcdesc}
{
b16decode
}{
s
\optional
{
, casefold
}}
Decode a Base16 encoded string.
\var
{
s
}
is the string to decode. Optional
\var
{
casefold
}
is a flag
specifying whether a lowercase alphabet is acceptable as input. For
security purposes, the default is
\code
{
False
}
.
The decoded string is returned. A
\exception
{
TypeError
}
is raised if
\var
{
s
}
were incorrectly padded or if there are non-alphabet
characters present in the string.
\end{funcdesc}
The legacy interface:
\begin{funcdesc}
{
decode
}{
input, output
}
\begin{funcdesc}
{
decode
}{
input, output
}
Decode the contents of the
\var
{
input
}
file and write the resulting
Decode the contents of the
\var
{
input
}
file and write the resulting
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment