[
https://issues.apache.org/jira/browse/HTTPCLIENT-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12584243#action_12584243
]
Tim Julien commented on HTTPCLIENT-741:
---
(working with Sam)
Yes, we no longer see
[
https://issues.apache.org/jira/browse/HTTPCLIENT-741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Julien updated HTTPCLIENT-741:
--
Attachment: additional_concurrency_fixes.patch
AbstractClientConnAdapter prone
Oleg Kalnichevski wrote:
On Sat, 2008-01-19 at 09:33 -0800, Sam Berlin wrote:
Here's my take. There is nothing wrong with j.u.URI as such. It just
needs a better parser that can deal with escaped and unescaped queries,
as well as be more lenient about common non-compliant behaviors, and
then
[
https://issues.apache.org/jira/browse/HTTPCLIENT-730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12561519#action_12561519
]
Tim Julien commented on HTTPCLIENT-730:
---
could probably steal
)
This ends up being a problem on http client 4.0, because the URI passed
in is reconstructed a few times under the covers by http client - using
the multi-arg constructors. I believe that the multi-arg constructors
have to be replaced with single-arg constructors.
-Tim Julien
