VERSION
version 1.018SYNOPSIS
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"
}
};
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. 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.
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!
AUTHORS
- Simon Cozens <[email protected]>
- Casey West <[email protected]>
- Ricardo SIGNES <[email protected]>
CONTRIBUTORS
- Matthew Green <[email protected]>
- Thomas Szukala <[email protected]>
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.