[
https://issues.apache.org/jira/browse/HTTPCORE-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532482
]
Roland Weber commented on HTTPCORE-112:
---------------------------------------
I often fail to communicate my thoughts properly. The parser framework is meant
to tie together the parsing done automatically in our framework, so the
framework can be customized. Thinking about it, there are a few cases where
HttpCore interprets headers. But those have to do with IO, which can be
customized already, or is encapsulated in interceptors which can be replaced.
So I don't see a need to customize header value parsing in the framework
itself. To me, it's on a different level.
My original concern about the parsing code were the static methods calling
eachother, which made it basically impossible to replace just a piece inside
without copying and changing everything around. (the piece in question being
the protocol name)
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]
