[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bogusly RFC2047'd "inline" for Content-Disposition
From: |
Robert Elz |
Subject: |
Re: Bogusly RFC2047'd "inline" for Content-Disposition |
Date: |
Sun, 27 Sep 2020 03:07:32 +0700 |
Date: Sat, 26 Sep 2020 17:09:36 +0100
From: Ralph Corderoy <ralph@inputplus.co.uk>
Message-ID: <20200926160936.731172209E@orac.inputplus.co.uk>
| that field does not parse so RFC 2183's
How do you know for sure? In this case it seems unlikely, but
any string could be "An extension token defined by a
standards-track RFC and registered
with IANA"
The code certainly isn't going to go look in the IANA registry to see
if some unknown string is registered there or not, all it is possible
to do is assume that it might have been.
kre