Shanti Suresh wrote:
Greetings,
On Wed, Jun 26, 2013 at 4:08 PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
André,
But, even when sending UTF-8 encoded data according to this
principle, they are *not* indicating that it is U
Greetings,
On Wed, Jun 26, 2013 at 4:08 PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> André,
>
>
>
> > But, even when sending UTF-8 encoded data according to this
> > principle, they are *not* indicating that it is UTF-8 da
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
André,
On 6/26/13 11:40 AM, André Warnier wrote:
> Shanti Suresh wrote:
>> Hi Chris,
>>
>> This is such an interesting discussion. I am not sure what to
>> make of this person's comment:
>>
>> --- TAXI 2012-10-09 09:03:59 PDT
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Shanti,
On 6/26/13 11:00 AM, Shanti Suresh wrote:
> Hi Chris,
>
> This is such an interesting discussion. I am not sure what to make
> of this person's comment:
>
> --- TAXI 2012-10-09 09:03:59 PDT
>
> Wow, no fix since 8 years
2013/6/26 Shanti Suresh :
> Hi Chris,
>
> This is such an interesting discussion. I am not sure what to make of this
> person's comment:
>
> ---
> TAXI 2012-10-09 09:03:59 PDT
>
> Wow, no fix since 8 years...
>
> And this is a real bug: If the HTTP header says the file is encoded
Shanti Suresh wrote:
Hi Chris,
This is such an interesting discussion. I am not sure what to make of this
person's comment:
---
TAXI 2012-10-09 09:03:59 PDT
Wow, no fix since 8 years...
And this is a real bug: If the HTTP header says the file is encoded in
ISO-8859-1 the co
Hi Chris,
This is such an interesting discussion. I am not sure what to make of this
person's comment:
---
TAXI 2012-10-09 09:03:59 PDT
Wow, no fix since 8 years...
And this is a real bug: If the HTTP header says the file is encoded in
ISO-8859-1 the common way to override th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
André,
On 6/26/13 8:01 AM, André Warnier wrote:
> Jan Vávra wrote:
>> Hello,
> When I create user with password with czech String
> "ŽežUlička.1" the browser sends correctly this string as:
>
> POST http://localhost:70/myapp/j_secur
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jan,
On 6/26/13 7:14 AM, Jan Vávra wrote:
> Hello,
When I create user with password with czech String
"ŽežUlička.1" the browser sends correctly this string as:
POST http://localhost:70/myapp/j_security_check HTTP/1.1
Conte
Jan Vávra wrote:
Hello,
When I create user with password with czech String "ŽežUlička.1" the
browser sends correctly this string as:
POST http://localhost:70/myapp/j_security_check HTTP/1.1
Content-Type: application/x-www-form-urlencoded
j_username=p&j_password=%C5%BDe%C5%BEUli%C4%8Dka.1
The
Hello,
When I create user with password with czech String "ŽežUlička.1" the
browser sends correctly this string as:
POST http://localhost:70/myapp/j_security_check HTTP/1.1
Content-Type: application/x-www-form-urlencoded
j_username=p&j_password=%C5%BDe%C5%BEUli%C4%8Dka.1
The browser is not sen
On 24/06/2013 12:52, Jan Vávra wrote:
>> Hello,
>>I'm successfully using form based authenntication when login or
>> password contains only letters from English alphabet.
OK. That means you've got the basics set up correctly.
>> I have also written own realm.
I'd suggest testing with the de
n xml file ?
De : Jan Vávra [va...@602.cz]
Envoyé : lundi 24 juin 2013 13:36
À : Tomcat Users List
Objet : FORM based authentication and utf-8 encoding of credentials
Hello,
I'm successfully using form based authenntication when login or
password contains only letters from E
Hello,
I'm successfully using form based authenntication when login or
password contains only letters from English alphabet. I have also
written own realm.
When I create user with password with czech String "ŽežUlička.1" the
browser sends correctly this string as:
POST http://localhost:70/
14 matches
Mail list logo
