dev@grizzly.java.net

Re: UTF8 encoding problem

From: Cam Bazz <cambazz_at_gmail.com>
Date: Wed, 25 Jun 2008 19:39:33 +0300

hello,

the request in question is a : com.sun.grizzly.tcp.Request

attached please find the adapter code.

Best,
-C.B.

On Wed, Jun 25, 2008 at 7:29 PM, Jeanfrancois Arcand <
Jeanfrancois.Arcand_at_sun.com> wrote:

> Salut,
>
> Cam Bazz wrote:
>
>> Hello,
>>
>> I made a simple http async request processor as described in
>> Jean-Francois's blog and hooked it up to a lucene index, so I can make
>> simple operations such as insert or delete from the index in a sync manner.
>>
>
> Interesting :-)
>
>
>> however I am using utf-8 fonts. I have been trying for a day, but I could
>> not find a solution to the font problem. the
>> request.setCharacterEncoding("UTF-8") does not have an effect.
>>
>> namely, I talk to the grizzly daemon from another servlet, which encodes
>> the uri parameters before sending it to grizzly daemon. basically for non
>> standard characters it sends %C4%C1 alike characters
>>
>> when the service(Request req, Response res) receives the uri, it wont
>> decode them properly.
>>
>> req.getParameters().getUndecodedParameter("paramName") will also return a
>> empty string.
>>
>
> Can you share a test case with me? Looks like a bug IMO. I know it works
> when you use GrizzlyRequest, so I need to understand why doing it directly
> using Request doesn't work.
>
> Thanks
>
> -- Jeanfrancois
>
>
>
>> (I could decode it on my own, if I knew the undecoded version)
>>
>> any ideas on this one?
>>
>> Best Regards,
>> -C.B.
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>
>