[
https://issues.apache.org/jira/browse/TIKA-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17805645#comment-17805645
]
Tim Allison commented on TIKA-4178:
-----------------------------------
In thinking about this some more, we could have the user signal to the /tika
and /rmeta endpoints that the user is sending a json description of the fetcher
rather than the actual file bytes. This would be far better than dealing with
the encoding issues of url or http header encoding limitations, erm, features.
What would be the elegant way of doing this? Something in the header request?
URL query parameter a bit better?
> HttpFetcher should handle encoded URLs properly
> -----------------------------------------------
>
> Key: TIKA-4178
> URL: https://issues.apache.org/jira/browse/TIKA-4178
> Project: Tika
> Issue Type: Bug
> Components: tika-pipes
> Reporter: Tim Allison
> Priority: Major
>
> On the user list, João Domingues reported that the HttpFetcher corrupts URLS,
> even ones that are properly encoded.
> https://lists.apache.org/thread/rlbyp4xymhsc3obrb6xsc3qq8w5n6jos
--
This message was sent by Atlassian Jira
(v8.20.10#820010)