You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tika.apache.org by "Nicholas DiPiazza (Jira)" <ji...@apache.org> on 2024/05/26 11:38:00 UTC

[jira] [Closed] (TIKA-4262) In pipes XML config, List serializes incorrect causing the parameters to be empty when read

     [ https://issues.apache.org/jira/browse/TIKA-4262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nicholas DiPiazza closed TIKA-4262.
-----------------------------------
      Assignee: Nicholas DiPiazza
    Resolution: Invalid

never mind - this was an issue in my branch reproducing in a crazy way.

> In pipes XML config, List<String> serializes incorrect causing the parameters to be empty when read
> ---------------------------------------------------------------------------------------------------
>
>                 Key: TIKA-4262
>                 URL: https://issues.apache.org/jira/browse/TIKA-4262
>             Project: Tika
>          Issue Type: Bug
>          Components: tika-pipes
>            Reporter: Nicholas DiPiazza
>            Assignee: Nicholas DiPiazza
>            Priority: Major
>
> tika configuration when saving a fetcher with a list of strings will look like this:
>       <httpHeaders>[]</httpHeaders>
>       <httpRequestHeaders>[Authorization: xyz123]</httpRequestHeaders>
> These are invalid format. It's expecting them to be:
>       <httpHeaders></httpHeaders>
>       <httpRequestHeaders>
>           <httpRequestHeader>Autorization: xyz123</httpRequestHeader>
>       </httpRequestHeaders>
> So the effect of this is all List<String> configs in fetchers are completely ignored after being saved/re-read.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)