[
https://issues.apache.org/jira/browse/HTTPCORE-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531593
]
Roland Weber commented on HTTPCORE-112:
---------------------------------------
Hi Oleg,
if it were any more complex than searching for a comma and stripping off
whitespace, I'd agree with you. But I somehow feel that the HeaderElements
interface and parsing is overkill for the cases where plain string tokens are
in the list.
The token iterator I proposed resides decoupled on top of the HeaderIterator.
How about adding an HeaderElementIterator in the same way, for the cases where
elements are not plain strings?
The dedicated iterator interfaces with specific nextXxx() methods do provide
strong typing. I fully agree that plain Iterator with the unavoidable downcasts
would be ugly.
cheers,
Roland
> DefaultConnectionReuseStrategy misinterprets Connection header
> --------------------------------------------------------------
>
> Key: HTTPCORE-112
> URL: https://issues.apache.org/jira/browse/HTTPCORE-112
> Project: HttpComponents Core
> Issue Type: Bug
> Components: HttpCore
> Affects Versions: 4.0-alpha5
> Reporter: Roland Weber
> Priority: Minor
> Fix For: 4.0-beta1
>
> Attachments: multiuconn.patch
>
>
> DefaultConnectionReuseStrategy assumes that "Connection:" is a single-valued
> header.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
