From: Ken Raeburn <raeburn@raeburn.org>
Cc: Marc Horowitz <marc@mit.edu>,
rms@gnu.org, bugs@gnus.org, emacs-devel@gnu.org
Subject: Re: base64 behavior is not MIME compliant
Date: Tue, 5 Jul 2005 21:15:04 -0400 [thread overview]
Message-ID: <e7023d30307e3db909bb5a25de0a313f@raeburn.org> (raw)
In-Reply-To: <87wto4j44m.fsf@kanga.tapsellferrier.co.uk>
On Jul 5, 2005, at 18:10, Nic Ferrier wrote:
> Why can't you just pre-parse the data parsed to the base64 decoder? I
> believe that's the correct behaviour. A base64 decoder should decode
> base64, not "base64 but also it does this extra trick if you wave your
> hand in the air"
Except "this extra trick" is specifically outlined as an option in the
base64 spec (RFC 3548), and MIME invokes that option. So proper "MIME
base64 decoding" would require this extra step of throwing away
characters that are not part of a base64 encoding, and then making a
second pass with the strict base64 decoder. In fact, as I read RFC
3548 section 2.3, the CR/LF line break sequences in MIME messages are
not part of the base64 alphabet, and therefore
fns.c:IS_BASE64_IGNORABLE already implements a limited form of what
Marc is asking for.
Ken
next prev parent reply other threads:[~2005-07-06 1:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <t53zmt4dce3.fsf@central-air-conditioning.toybox.cambridge.ma.us>
2005-07-03 20:43 ` base64 behavior is not MIME compliant Richard M. Stallman
2005-07-03 21:09 ` Nic Ferrier
2005-07-04 4:59 ` Marc Horowitz
2005-07-05 4:35 ` Richard M. Stallman
2005-07-05 21:35 ` Marc Horowitz
2005-07-05 22:10 ` Nic Ferrier
2005-07-05 23:55 ` Marc Horowitz
2005-07-06 1:06 ` Nic Ferrier
2005-07-06 1:15 ` Ken Raeburn [this message]
2005-07-06 1:48 ` Nic Ferrier
2005-07-05 22:52 ` Arne Jørgensen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e7023d30307e3db909bb5a25de0a313f@raeburn.org \
--to=raeburn@raeburn.org \
--cc=bugs@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=marc@mit.edu \
--cc=rms@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).