[ https://issues.apache.org/jira/browse/TIKA-4262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nicholas DiPiazza updated TIKA-4262: ------------------------------------ Description: 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. was: 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> > 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 > 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)