And Python uses RFC 4648
- the “default” encoder (“b64encode”) will pad the output
- although it will not linebreak (“encodebytes”) does that)
- the default decoder will error if the input is not padded
- the default decoder will ignore all non-encoding characters by default
Also both b64encode and encodebytes actually use binascii.b2a_base64, which claims conformance to RFC 3548, which attempts to unify 1421 and 2045. Except RFC 3548 requires rejecting non-encoding data, whereas (again) Python accepts an ignores it by default, in 2045 fashion.
Still more robust than uuencode though.
> Lines of Quoted-Printable encoded data must not be longer than 76 characters. To satisfy this requirement without altering the encoded text, soft line breaks may be added as desired. A soft line break consists of an =
IIUC in Base64 you can throw whichever white space anywhere and it should be ignored. And in URL ("percent") encoding there is no insignificant white space possible (?) and encoding of white space depends on implementation (dreaded space `%20` vs ` ` vs `+` in application/x-www-form-urlencoded [2]).
[1] https://en.wikipedia.org/wiki/Quoted-printable [2] https://en.wikipedia.org/wiki/Percent-encoding
.-_ would have been a better choice tha +/=
GET /your/path-to/the.file HTTP/1.1