[
https://issues.apache.org/jira/browse/TIKA-4644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Allison resolved TIKA-4644.
-------------------------------
Fix Version/s: 4.0.0
Resolution: Fixed
> add /config to path for legacy endpoints that allow a config
> ------------------------------------------------------------
>
> Key: TIKA-4644
> URL: https://issues.apache.org/jira/browse/TIKA-4644
> Project: Tika
> Issue Type: Task
> Components: tika-server
> Reporter: Tim Allison
> Priority: Minor
> Fix For: 4.0.0
>
>
> I had overloaded /tika and other legacy endpoints to handle with and without
> a config. Allowing configs is dangerous, and we should use a separate path so
> that nginx or other proxies know to require auth.
> Let's add /config ... so /tika/config /rmeta/config /unpack/config and
> /detect/config.
> We'll also require "enableUnsecureFeatures" for these config endpoints so
> that users understand the risks.
> This is only for 4.x
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
