From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: Parsing Content-Type with repeated attributes
Date: Tue, 12 Oct 2010 23:33:02 +0200 [thread overview]
Message-ID: <m3ocaz5c6p.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87eibv453u.fsf@engster.org>
David Engster <deng@randomsample.de> writes:
> OK, I've read (well, rather skimmed) the RFC, and it defines a
> continuation of MIME parameters through the asterisk, followed by a
> number:
>
> URL*0="ftp://";
> URL*1="cs.utk.edu/pub/moore/bulk-mailer/bulk-mailer.tar"
>
> Otherwise, I don't see that you should concatenate parameter
> values. Actually, I couldn't find any specification of what should be
> done when parameters are defined several times.
It seems wrong to concatenate them, anyway. I've now made the code
ignore any repetitions.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2010-10-12 21:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 12:11 David Engster
2010-10-11 18:21 ` Lars Magne Ingebrigtsen
2010-10-12 18:51 ` David Engster
2010-10-12 21:33 ` Lars Magne Ingebrigtsen [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3ocaz5c6p.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).