[
https://issues.apache.org/jira/browse/TIKA-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15766074#comment-15766074
]
Derek Hardison edited comment on TIKA-1788 at 12/21/16 4:24 AM:
----------------------------------------------------------------
The * indicates the name is wrapped and it can be any number of
continuations... i.e. filename*0, filename*1, etc. will end up being
concatenated into a single filename... then there are some rules on where the
content-type etc is located when that happens. You can find examples fairly
easy.... i.e. exchange or gmail e-mails.
You can find some information about it here;
- https://tools.ietf.org/html/rfc2231#section-4
- https://tools.ietf.org/html/rfc5987#section-3.2.2
was (Author: derek.hardison):
The * indicates the name is wrapped and it can be any number of
continuations... i.e. filename*0, filename*1, etc.
You can find some information about it here;
- https://tools.ietf.org/html/rfc2231#section-4
- https://tools.ietf.org/html/rfc5987#section-3.2.2
> message/rfc822 parser doesn't identify attachment filenames from
> Content-Disposition header
> -------------------------------------------------------------------------------------------
>
> Key: TIKA-1788
> URL: https://issues.apache.org/jira/browse/TIKA-1788
> Project: Tika
> Issue Type: Bug
> Affects Versions: 1.11
> Reporter: Sergey Tsalkov
> Attachments: grep_content_disposition.zip
>
>
> rfc822 email files can contain attachments as subparts, and they'll
> generally specify the filename of the attachment in a manner like
> this:
> Content-Disposition: attachment;
> filename*=utf-8''image001.jpg
> Tika doesn't seem to be grabbing that information at all!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
