From: David Engster <deng@randomsample.de>
To: ding@gnus.org
Subject: Re: Parsing Content-Type with repeated attributes
Date: Tue, 12 Oct 2010 20:51:17 +0200 [thread overview]
Message-ID: <87eibv453u.fsf@engster.org> (raw)
In-Reply-To: <m3zkukd1za.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Mon, 11 Oct 2010 20:21:45 +0200")
Lars Magne Ingebrigtsen writes:
> David Engster <deng@randomsample.de> writes:
>
>> ("content-type:application/x-pkcs7-mime"
>> (name . "smime.p7msmime.p7m")
>> (smime-type . "signed-datasigned-data"))
>>
>> I first thought this was a bug, but it seems the above rfc2231 function
>> concats those strings very deliberately...
>
> I dimly seem to remember that being specified by the RFC.
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.
-David
next prev parent reply other threads:[~2010-10-12 18:51 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 [this message]
2010-10-12 21:33 ` Lars Magne Ingebrigtsen
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=87eibv453u.fsf@engster.org \
--to=deng@randomsample.de \
--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).