[jdev] base64 line endings

Matthew A. Miller linuxwolf at outer-planes.net
Wed Apr 19 11:51:09 CDT 2006


Because some implementations can't do the equivalent of "s/\s+//g" 
before decoding?

I don't think it's all that difficult to first strip all whitespace from 
the base64-encoded text before passing it through the decoder.

/me shrugs

Peter Saint-Andre wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Kevin Smith wrote:
> 
>>On 19 Apr 2006, at 13:43, Norman Rasmussen wrote:
>>
>>>1. Most clients add line feeds.
>>>2. JEP-0153 via rfc-2045 suggests adding line feeds.
>>>3. xs:base64Binary spec, via rfc-2045 suggests adding line feeds.
>>>
>>>My preferred result to this would be to change the JEP's to say line
>>>feeds SHOULD not be added, but they MUST be accepted.
>>
>>What was the reason for discouraging them in the first place?
> 
> 
> I don't remember.
> 
> P
> 
> - --
> Peter Saint-Andre
> Jabber Software Foundation
> http://www.jabber.org/people/stpeter.shtml
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> 
> iD8DBQFERmahNF1RSzyt3NURAky1AKCakowPvPccGZj1QzEihMjE9E/VDwCeLrEO
> T0njI+AuLFQWOmvWmaUMZ30=
> =R6Pa
> -----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3543 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/jdev/attachments/20060419/8002d338/attachment-0002.bin>


More information about the JDev mailing list