Re: Utf-8 encoded redirect url results in Invalid redirect URI and Illegal character in path (URISyntaxException)

2010-10-25 Thread John Smith
On Mon, Oct 25, 2010 at 11:51 AM, Oleg Kalnichevski 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 > Thanks yo

Re: Utf-8 encoded redirect url results in Invalid redirect URI and Illegal character in path (URISyntaxException)

2010-10-25 Thread Oleg Kalnichevski
On Sat, 2010-10-23 at 02:40 +0330, John Smith wrote: ... > > Oleg, > > Thanks for quick response, but I have not found any way to reformat an > incorrectly encoded string. I doubt that this possible at all. > > Is there any way to make HttpClient read headers as UTF-8 (even with > modification

Re: Utf-8 encoded redirect url results in Invalid redirect URI and Illegal character in path (URISyntaxException)

2010-10-22 Thread John Smith
On Sat, Oct 23, 2010 at 1:34 AM, Oleg Kalnichevski 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. >> > > U

Re: Utf-8 encoded redirect url results in Invalid redirect URI and Illegal character in path (URISyntaxException)

2010-10-22 Thread Oleg Kalnichevski
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. HttpCl

Re: Utf-8 encoded redirect url results in Invalid redirect URI and Illegal character in path (URISyntaxException)

2010-10-22 Thread John Smith
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 in