asbachb wrote:
Thanks for you reply.
I checked my clients request to tomcat which shows that the umlauts are
correctly replaced with their enities:
GET
"http://localhost:8080/wicket-umlauts-1.0-SNAPSHOT/page/param/v%C3%A4lue-xxx";
This request should be a valid ASCII request and shouldn't be a
Thanks for you reply.
I checked my clients request to tomcat which shows that the umlauts are
correctly replaced with their enities:
GET
"http://localhost:8080/wicket-umlauts-1.0-SNAPSHOT/page/param/v%C3%A4lue-xxx";
This request should be a valid ASCII request and shouldn't be a problem to
deco
asbachb wrote:
Thank you for you reply.
Sorry for expressing me a little vague. I meant that i alread tried both
attributes.
My used encoding is UTF-8.
Here are the missing sources:
http://old.nabble.com/file/p30775449/wicket-umlauts.zip wicket-umlauts.zip
Konstantin Kolinko wrote:
201
Thank you for you reply.
Sorry for expressing me a little vague. I meant that i alread tried both
attributes.
My used encoding is UTF-8.
Here are the missing sources:
http://old.nabble.com/file/p30775449/wicket-umlauts.zip wicket-umlauts.zip
Konstantin Kolinko wrote:
>
> 2011/1/27 asbachb
2011/1/27 asbachb :
> Like mentioned in the CharacterEncoding FAQs I already setup URIEncoding and
> useBodyEncodingForURI attribute in my server.xml configuration.
URIEncoding and useBodyEncodingForURI are alternatives. Do not use
both at the same time. My understanding of /docs/config/http.htm
Hello,
Environment: Tomcat 7.0.6 - Java 1.6_22 - Ubuntu 10.10
I got some problems with a wicket application which decodes parameters into
path of the uri. When calling getServletPath() on that uris, containig
umlauts the method will return some wrong encoded path.
In my sample application the me
