Hi Mike,
your quick and easy patch fixes the problem right away. For my problem it
is good to go!
Thanks for the quick response and solution.
Olaf
P.S. Using UTF-8 does no good, I had tried this before.
Michael Becke [EMAIL PROTECTED] wrote on 13.11.2003 03:59:43:
Hello Olaf,
Here's a
[EMAIL PROTECTED] wrote:
byte bytes[] = new byte[ (n)];
bytes = text.getBytes();
Bravo, the above code couldn't be worse...
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
Hi,
today an administrator reported a password related problem within one of
our applications to me. I tracked down the problem that the user had used
the german Umlaute äöü in his password.
Our application tried to log in to another web site using a get method from
HTTPClient 2.0 rc2 setting
This would appear to be a character encoding issue.
In BasicScheme.authenticate, it currently does this:
return Basic + HttpConstants.getAsciiString(
Base64.encode(HttpConstants.getBytes(buffer.toString(;
I suspect it should be doing something like this:
return Basic +
Hello Olaf,
Here's a quick patch that fixes the immediate problem. From reading
RFC 2616 and 2617 it seems to me that we should have been using
ISO-8859-1 as the encoding instead of US-ASCII. Please give this patch
a try.
Mike
On Nov 12, 2003, at 3:32 PM, [EMAIL PROTECTED] wrote:
Hi,
As per usual the patch was stripped. I will attach it to bugzilla.
Mike
On Nov 12, 2003, at 9:59 PM, Michael Becke wrote:
Hello Olaf,
Here's a quick patch that fixes the immediate problem. From reading
RFC 2616 and 2617 it seems to me that we should have been using
ISO-8859-1 as the
