[
https://issues.apache.org/jira/browse/HTTPASYNC-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13935091#comment-13935091
]
Oleg Kalnichevski commented on HTTPASYNC-72:
--------------------------------------------
Common browsers have layers and layers of code intended to deal with all kinds
of insanity one can come across on the web. HttpClient is not a browser, it is
a transport library. It is not supposed to make guesses about things absolutely
clearly defined by the spec. Having said that, HttpClient can be customized a
great deal. One can force it to use UTF-8 (or any other charset supposed by
java) instead of ASCII for HTTP message elements. One can customize the way
redirect location is concerted to a valid URI, and so on. However, all these
decisions tend to be application specific and while some protocol deviations
may be appropriate in one context they may be completely inappropriate in
others.
Oleg
> 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: [email protected]
For additional commands, e-mail: [email protected]
