| Subject: | Request to use mime attribute content-location to determine recommended filename |
| Date: | Sun, 2 Sep 2012 22:34:38 +1000 |
| To: | bug-MIME-tools [...] rt.cpan.org |
| From: | John Murphy <john.softek [...] gmail.com> |
Hi,
RFC 2557 MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)
provides a means of specifying the name and location of an attachment.
This document a) defines the use of a MIME multipart/related
structure to aggregate a text/html root resource and the subsidiary
resources it references, and b) specifies a MIME content-header
(Content-Location) that allow URIs in a multipart/related text/html
root body part to reference subsidiary resources in other body parts
of the same multipart/related structure.
Example:
----=_rsvp_irot_part_1311710291l.0xabe91c30
Content-Type: image/gif
Content-Transfer-Encoding: base64
Content-Location: genImages/attach_1.gif
You could accommodate this convention by changing this line in sub
recommended_filename in Head.pm from:
foreach my $attr_name ( qw( content-disposition.filename content-type.name)
) {
to:
foreach my $attr_name ( qw( content-disposition.filename
content-type.namecontent-location) ) {
Regards,
John Murphy