[
https://issues.apache.org/jira/browse/HTTPASYNC-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13935269#comment-13935269
]
Oleg Kalnichevski commented on HTTPASYNC-72:
--------------------------------------------
I might be missing an intrigue here, but I think it is blatantly obvious from
RFC 2616
{noformat}
14.30 Location
The Location response-header field is used to redirect the recipient
to a location other than the Request-URI for completion of the
request or identification of a new resource. For 201 (Created)
responses, the Location is that of the new resource which was created
by the request. For 3xx responses, the location SHOULD indicate the
server's preferred URI for automatic redirection to the resource. The
field value consists of a single absolute URI.
Location = "Location" ":" absoluteURI
{noformat}
absoluteURI is defined as
{noformat}
3.2.1 General Syntax
URIs in HTTP can be represented in absolute form or relative to some
known base URI [11], depending upon the context of their use. The two
forms are differentiated by the fact that absolute URIs always begin
with a scheme name followed by a colon. For definitive information on
URL syntax and semantics, see "Uniform Resource Identifiers (URI):
Generic Syntax and Semantics," RFC 2396 [42] (which replaces RFCs
1738 [4] and RFC 1808 [11]). This specification adopts the
definitions of "URI-reference", "absoluteURI", "relativeURI", "port",
"host","abs_path", "rel_path", and "authority" from that
specification.
{noformat}
> 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
