[
https://issues.apache.org/jira/browse/NUTCH-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Nagel reassigned NUTCH-3002:
--------------------------------------
Assignee: Sebastian Nagel
> Protocol-okhttp HttpResponse: HTTP header metadata lookup should be
> case-insensitive
> ------------------------------------------------------------------------------------
>
> Key: NUTCH-3002
> URL: https://issues.apache.org/jira/browse/NUTCH-3002
> Project: Nutch
> Issue Type: Bug
> Components: metadata, plugin, protocol
> Affects Versions: 1.19
> Reporter: Sebastian Nagel
> Assignee: Sebastian Nagel
> Priority: Major
> Fix For: 1.20
>
>
> Lookup of HTTP headers in the class HttpResponse should be case-insensitive -
> for example, any "Location" header should be returned independent from the
> casing sent by the sender.
> While protocol-http uses the class SpellCheckedMetadata which provides
> case-insensitive lookups (as part of the spell-checking functionality),
> protocol-okhttp relies on the class Metadata which stores the metadata values
> case-sensitive.
> It's a good question, whether we still need to spell-check HTTP headers.
> However, case-insensitive look-ups are definitely required. Especially, since
> HTTP header names are case-insensitive in HTTP/2.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
