[
https://issues.apache.org/jira/browse/TIKA-3133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17157451#comment-17157451
]
ASF GitHub Bot commented on TIKA-3133:
--------------------------------------
nddipiazza commented on pull request #326:
URL: https://github.com/apache/tika/pull/326#issuecomment-658236941
@tballison i think this can be merged now. I disassociated it with TIKA-3126
so that this PR can be 100% focused on not hard coding those values.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> /rmeta endpoint should not hard code writeLimit and maxEmbeddedResources
> ------------------------------------------------------------------------
>
> Key: TIKA-3133
> URL: https://issues.apache.org/jira/browse/TIKA-3133
> Project: Tika
> Issue Type: Improvement
> Components: server
> Reporter: Nicholas DiPiazza
> Priority: Trivial
>
> When parsing using /rmeta endpoint, you are stuck with the unlimited
> writeLimit and unlimited number of maxEmbeddedResources
> We should add these as optional headers that allow us to control that
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
