[
https://issues.apache.org/jira/browse/HTTPASYNC-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13935073#comment-13935073
]
Rainer Hind commented on HTTPASYNC-72:
--------------------------------------
Thanks for the pointer. Will look to see where to hook in a custom strategy.
While I agree it's not compliant with the RFC, Google Chrome manages to
correctly interpret it so it can't be complete garbage.
It's actually the Facebook server (at fb.me) returning the faulty header,
probably with UTF-8 encoding instead of escaped characters.
It may be worth considering if this isn't a more widespread problem.
> Connecting to certain URLs causes a malformedInputException
> ------------------------------------------------------------
>
> Key: HTTPASYNC-72
> URL: https://issues.apache.org/jira/browse/HTTPASYNC-72
> Project: HttpComponents HttpAsyncClient
> Issue Type: Bug
> Affects Versions: 4.0-beta4
> Environment: Ubuntu 13.10
> Reporter: Rainer Hind
> Priority: Minor
> Attachments: Bug.java
>
>
> When attempting to get the future object after executing a request, a
> malformedInputException is thrown. I believe this is due to non-ascii
> characters in the location header (since the page in the example code is a
> Thai website, with Thai characters in the URL).
> When connecting to the problem site, there is no issue. However, when
> connecting to a site which redirects to the problem site, the exception is
> thrown.
> See the attached code for an example.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org
