[
https://issues.apache.org/jira/browse/HTTPASYNC-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13935254#comment-13935254
]
Sebb commented on HTTPASYNC-72:
-------------------------------
Is it documented anywhere that the Location string must be encoded?
I've just been looking at the Apache Httpd doc for Redirect (1)
This says
{quote}
The old URL-path is a case-sensitive (%-decoded) path beginning with a slash. A
relative path is not allowed.
The new URL may be either an absolute URL beginning with a scheme and hostname,
or a URL-path beginning with a slash. In this latter case the scheme and
hostname of the current server will be added.
{quote}
Unfortunately this does not say anything about the encoding state of the new URL
(1) http://httpd.apache.org/docs/2.4/mod/mod_alias.html#Redirect
> 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
