-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 1/24/2010 9:22 AM, André Warnier wrote:
> Christopher Schultz wrote:
>
>> Maybe all character sets have bytes 0-127 the same as US-ASCII, but I
>> don't know about some of those I never see myself: Shift-JS and all
>> those Asian encodings,
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
(Marking OT because, well... just because).
On 1/22/2010 2:59 PM, Warnier wrote:
Christopher Schultz wrote:
That "authorization.getBytes()" is just asking for trouble, because it
uses the platform default encodin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
(Marking OT because, well... just because).
On 1/22/2010 2:59 PM, Warnier wrote:
> Christopher Schultz wrote:
>> That "authorization.getBytes()" is just asking for trouble, because it
>> uses the platform default encoding to convert characters
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 1/21/2010 6:35 PM, André Warnier wrote:
Basically, I would tend to say that if the server knows who the clients
are and vice-versa, you should be free to use any encoding you want,
with the limitation that what
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 1/21/2010 6:35 PM, André Warnier wrote:
> Basically, I would tend to say that if the server knows who the clients
> are and vice-versa, you should be free to use any encoding you want,
> with the limitation that what is exchanged on the wire
To get back to the underlying issue :
Auth Gábor wrote:
So... this is the real chaos... :)
Yes.
By the way, my users are not use HTML browsers, they are using JAX-WS in their
client program, and the JAX-WS sends authentication data in UTF-8 (like
Opera), because the default encoding is U
Christopher Schultz wrote:
...
Nice that someone looked at actual behavior of the browsers.
There is an easy way to find out what really happens.
Gábor,
I presume that you have a workstation set for iso-8859-2 (or whichever
non iso-8859-1 charset is appropriate for Magyar, I forgot), and a
b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gábor,
On 1/21/2010 9:16 AM, Auth Gábor wrote:
> Mark Thomas wrote:
>>OCTET =
>>CTL= > (octets 0 - 31) and DEL (127)>
>>
>> So actually, Tomcat is correct in the current treatment of creden
Hi,
Mark Thomas wrote:
>OCTET =
>CTL= (octets 0 - 31) and DEL (127)>
>
> So actually, Tomcat is correct in the current treatment of credentials.
> Therefore, not a bug.
Yes, but the UTF-8 encoded text is contains any 8-bit sequence o
Mark Thomas wrote:
On 21/01/2010 06:55, André Warnier wrote:
Mark Thomas wrote:
The authorisation header is base64
encoded so it is automatically compliant with RFC2616.
Yes, it sounds like you're right; my mistake.
(Also for Gabor, I admit my mistake.)
I agree that the HTTP header itself is
On 21/01/2010 06:55, André Warnier wrote:
> Mark Thomas wrote:
>> The authorisation header is base64
>> encoded so it is automatically compliant with RFC2616.
>>
> Yes, it sounds like you're right; my mistake.
> (Also for Gabor, I admit my mistake.)
>
> I agree that the HTTP header itself is corre
Mark Thomas wrote:
On 21/01/2010 06:12, André Warnier wrote:
Auth Gábor wrote:
Hi,
I've found a potential bug in the Basic Authentication module. I have
users and some user's username is contains national characters
(encoded in UTF-8). The HTTP header based authentication is fails when
the use
On 21/01/2010 06:12, André Warnier wrote:
> Auth Gábor wrote:
>> Hi,
>>
>> I've found a potential bug in the Basic Authentication module. I have
>> users and some user's username is contains national characters
>> (encoded in UTF-8). The HTTP header based authentication is fails when
>> the usernam
Hi,
André Warnier wrote:
>> I've found a potential bug in the Basic Authentication module. I have
>> users and some user's username is contains national characters (encoded
>> in UTF-8). The HTTP header based authentication is fails when the
>> username or the password contains multibyte character
On 21/01/2010 05:54, Auth Gábor wrote:
> Hi,
>
> I've found a potential bug in the Basic Authentication module. I have users
> and some user's username is contains national characters (encoded in UTF-8).
> The HTTP header based authentication is fails when the username or the
> password contain
Auth Gábor wrote:
Hi,
I've found a potential bug in the Basic Authentication module. I have users
and some user's username is contains national characters (encoded in UTF-8).
The HTTP header based authentication is fails when the username or the
password contains multibyte characters.
The r
Hi,
I've found a potential bug in the Basic Authentication module. I have users
and some user's username is contains national characters (encoded in UTF-8).
The HTTP header based authentication is fails when the username or the
password contains multibyte characters.
The root of the bug is the
17 matches
Mail list logo
