[
https://issues.apache.org/jira/browse/HTTPCORE-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531337
]
Roland Weber commented on HTTPCORE-112:
---------------------------------------
Folks, please check the specification of the Connection header in RFC 2616,
section 14.10:
HTTP/1.1 proxies MUST parse the Connection header field before a
message is forwarded and, for each connection-token in this field,
remove any header field(s) from the message with the same name as the
connection-token.
and also the definition of hop-by-hop headers in section 13.5.1:
The following HTTP/1.1 headers are hop-by-hop headers:
[snip]
Other hop-by-hop headers MUST be listed in a Connection header,
(section 14.10) to be introduced into HTTP/1.1 (or later).
There is only one token that has a meaning by itself, which is "close". All
other tokens are the names of the hop-by-hop header fields that are not in the
predefined list and that must be removed by proxies. There is no ambiguity
whatsoever. The keep-alive in my example is just a header name (that happens to
be in the predefined list).
I'm not suggesting to reassemble headers, I'm only asking that the list
mandated by RFC 2616 be interpreted correctly. And since it is not the only
case where the header value is a comma-separated list of tokens, I suggested to
implement a generic mechanism for that purpose.
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]
