Hello,
thanks for the reply. There were query parameters.
Meanwhile I've solved the problem. I had to read in the client HTTP
header field with the charset. You can also use
org.apache.http.util.EntityUtils
http://hc.apache.org/httpcomponents-core-ga/httpcore/apidocs/index.html.
Regards,
Robert
2011/10/11 Jakub Podlesak <jakub.podlesak_at_oracle.com>:
> Hi Robert,
>
> Could you be more specific on your use case?
> Is it query parameter or an entity parameter?
>
> Do you run this on a non UTF-8 enabled operating system?
> Client and server running on the same machine?
>
> Things should work just fine regarding character encoding
> (just did some quick manual tests and also having some tests
> being run continuously to cover this area). This could be
> environment configuration glitch, but it is hard to tell
> without some more details.
>
> Thanks,
>
> ~Jakub
>
> On 9.10.2011 13:09, Robert Naczinski wrote:
>>
>> Hello,
>>
>> how can set in Jersey, the server code page?
>>
>> I use testing framework with Jersey and Grizzly I send parameters to
>> my resource is a string containing special characters (German
>> umlauts). It depends on the server correctly, only the client gets
>> wrong bytes answer . (I believe ISO-8899-1)
>>
>> I want to run all the way UTF-8.
>>
>> Can someone give me a hint?
>>
>> Regards,
>>
>> Robert
>>
>