s as
https://vimeo.com/api/v2/ÐÑÑоÑкина/info.xml, and then the
URIParser throws "java.net.URISyntaxException: Illegal character in path at
index 26", which leads the DefaultRedirectStrategy to throw a
"org.apache.http.ProtocolException:
Invalid redirect URI".
Is this reall
On Mon, Oct 25, 2010 at 11:51 AM, Oleg Kalnichevski ol...@apache.org wrote:
One can set the 'http.protocol.element-charset' parameter to make
HttpClient use a specific charset for protocol elements
http://hc.apache.org/httpcomponents-client-ga/tutorial/html/fundamentals.html#d4e337
Oleg
Hi
I'm receiving an utf-8 encoded redirect url's from a website, but it
seems that httpclient (?) treat them as US-ASCII (?) so it can not
handle them correctly.
Is there any way to correct this behavior? Or is there any way to
convert incorrectly encoded string back to correct one (to be used
On Sat, 2010-10-23 at 01:24 +0330, John Smith wrote:
Hi
I'm receiving an utf-8 encoded redirect url's from a website, but it
seems that httpclient (?) treat them as US-ASCII (?) so it can not
handle them correctly.
URLs are not meant to have any characters other than US-ASCII.
On Sat, Oct 23, 2010 at 1:34 AM, Oleg Kalnichevski ol...@apache.org wrote:
On Sat, 2010-10-23 at 01:24 +0330, John Smith wrote:
Hi
I'm receiving an utf-8 encoded redirect url's from a website, but it
seems that httpclient (?) treat them as US-ASCII (?) so it can not
handle them correctly.