[
https://issues.apache.org/jira/browse/TIKA-3695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17511180#comment-17511180
]
Julien Massiera commented on TIKA-3695:
---------------------------------------
It is a good idea to set a hard limit on the maximum field length to be > the
longest mime type. This would avoid cases like the one we had with the docx
that a user could not easily understand !
Concerning the includeFields, I see no reason to not apply limit on the field
size. This section would only be there to prevent fields from being removed if
maxKey < includeField key, but the field size must be limited to avoid DoS
which is the main goal of those modifications
> LimitingMetadataFilter
> ----------------------
>
> Key: TIKA-3695
> URL: https://issues.apache.org/jira/browse/TIKA-3695
> Project: Tika
> Issue Type: New Feature
> Components: metadata
> Affects Versions: 1.28.1, 2.3.0
> Reporter: Julien Massiera
> Priority: Major
> Fix For: 2.4.0
>
> Attachments: huge-title.docx, tika-config.xml
>
>
> Some files may contain abnormally big metadata (several MB, be it for the
> metadata values, the metadata names, but also for the total amount of
> metadata) that can be problematic concerning the memory consumption.
> It would be great to develop a new LimitingMetadataFilter so that we can
> filter out the metadata according to different bytes limits (on metadata
> names, metadata values and global amount of metadata)
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
