At Sat, 26 Mar 2022 18:41:39 +0100, Magnus Hagander <magnus@hagander.net> wrote in
> The problem is that:
> 1. It's not an attachment. That is:
> Content-Disposition: inline; filename="0001-doc_wip-diff.txt"
> explicitly says it's not an attachment.
RFC2183 says that the header suggests how the multipart body is
displayed, not what it is.
https://www.ietf.org/rfc/rfc2183.txt
> 4. Summary
>
> Content-Disposition takes one of two values, `inline' and
> `attachment'. `Inline' indicates that the entity should be
> immediately displayed to the user, whereas `attachment' means that
> the user should take additional action to view the entity.
>
> The `filename' parameter can be used to suggest a filename for
> storing the bodypart, if the user wishes to store it in an external
> file.
Doesn't the fact that the Contnet-Disposition has the "filename"
attribute suggests the part is stored as an external content apart
from the difference between inline and attachement?
--
Kyotaro Horiguchi
NTT Open Source Software Center
