Re: MIME::Base64 bugs?
- From: liol <igor.lobanov@xxxxxxxxx>
- Date: Mon, 18 Jun 2007 11:17:11 -0000
On Jun 5, 2:21 pm, "sonet" <sonet....@xxxxxxxxxxxxx> wrote:
The MIME::Base64 will convert \n to \r\n.
$a="1234\n4567\n";
$a=encode_base64($a,0);
print decode_base64($a);
The result is 1234\r\n4567\r\n.
Look for http://www.ietf.org/rfc/rfc2045.txt [Page 25]
Care must be taken to use the proper octets for line breaks if
base64
encoding is applied directly to text material that has not been
converted to canonical form. In particular, text line breaks must
be
converted into CRLF sequences prior to base64 encoding. The
important thing to note is that this may be done directly by the
encoder rather than in a prior canonicalization step in some
implementations.
This RFC requirement.
Regards, LIOL
.
- Follow-Ups:
- Re: MIME::Base64 bugs?
- From: Peter J. Holzer
- Re: MIME::Base64 bugs?
- References:
- MIME::Base64 bugs?
- From: sonet
- MIME::Base64 bugs?
- Prev by Date: Re: DBI/DBD-Oracle and Proxy
- Next by Date: Installation error for module in CentOS 5.0 for HTML::Mason
- Previous by thread: Re: MIME::Base64 bugs?
- Next by thread: Re: MIME::Base64 bugs?
- Index(es):
Relevant Pages
|
