Email::MIME::ContentType(3pm) User Contributed Perl Documentation Email::MIME::ContentType(3pm) NAME Email::MIME::ContentType - Parse a MIME Content-Type or Content-Disposition Header VERSION version 1.022 SYNOPSIS use Email::MIME::ContentType; # Content-Type: text/plain; charset="us-ascii"; format=flowed my $ct = 'text/plain; charset="us-ascii"; format=flowed'; my $data = parse_content_type($ct); $data = { type => "text", subtype => "plain", attributes => { charset => "us-ascii", format => "flowed" } }; # Content-Type: application/x-stuff; # title*0*=us-ascii'en'This%20is%20even%20more%20; # title*1*=%2A%2A%2Afun%2A%2A%2A%20; # title*2="isn't it!" my $ct = q(application/x-stuff; title*0*=us-ascii'en'This%20is%20even%20more%20; title*1*=%2A%2A%2Afun%2A%2A%2A%20; title*2="isn't it!"); my $data = parse_content_type($ct); $data = { type => "application", subtype => "x-stuff", attributes => { title => "This is even more ***fun*** isn't it!" } }; # Content-Disposition: attachment; filename=genome.jpeg; # modification-date="Wed, 12 Feb 1997 16:29:51 -0500" my $cd = q(attachment; filename=genome.jpeg; modification-date="Wed, 12 Feb 1997 16:29:51 -0500"); my $data = parse_content_disposition($cd); $data = { type => "attachment", attributes => { filename => "genome.jpeg", "modification-date" => "Wed, 12 Feb 1997 16:29:51 -0500" } }; FUNCTIONS parse_content_type This routine is exported by default. This routine parses email content type headers according to section 5.1 of RFC 2045 and also RFC 2231 (Character Set and Parameter Continuations). It returns a hash as above, with entries for the "type", the "subtype", and a hash of "attributes". For backward compatibility with a really unfortunate misunderstanding of RFC 2045 by the early implementors of this module, "discrete" and "composite" are also present in the returned hashref, with the values of "type" and "subtype" respectively. parse_content_disposition This routine is exported by default. This routine parses email Content-Disposition headers according to RFC 2183 and RFC 2231. It returns a hash as above, with entries for the "type", and a hash of "attributes". WARNINGS This is not a valid content-type header, according to both RFC 1521 and RFC 2045: Content-Type: type/subtype; If a semicolon appears, a parameter must. "parse_content_type" will carp if it encounters a header of this type, but you can suppress this by setting $Email::MIME::ContentType::STRICT_PARAMS to a false value. Please consider localizing this assignment! Same applies for "parse_content_disposition". AUTHORS o Simon Cozens <simon AT cpan.org> o Casey West <casey AT geeknest.com> o Ricardo SIGNES <rjbs AT cpan.org> CONTRIBUTORS o Matthew Green <mrg AT eterna.au> o Pali <pali AT cpan.org> o Thomas Szukala <ts AT abusix.com> COPYRIGHT AND LICENSE This software is copyright (c) 2004 by Simon Cozens. This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself. perl v5.26.1 2017-09-18 Email::MIME::ContentType(3pm)
Generated by $Id: phpMan.php,v 4.55 2007/09/05 04:42:51 chedong Exp $ Author: Che Dong
On Apache
Under GNU General Public License
2024-04-25 02:11 @3.15.225.173 CrawledBy Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)