Hello!
I am having a problem with the double-encoding of Japanese characters
that are in the query string. For example:
http://www.example.com/path/q=日本語
If I write the raw value directly in the URL string in my browser,
there are no problems. If I write the URL encoded value directly
Ok, this seems to have something to do with proxying, not Wicket.
When I enter 日本語 into the form, Wicket correctly sends back the
reply:
HTTP/1.1 302
Location: http://www.example.com/path?q=%E6%97%A5%E6%9C%AC%E8%AA%9E
To which my browser redirects with:
GET
Ok, sorry for the noise.
I just needed to add the [NE] rule to my RewriteRule in my apache
config and that did the trick.
Cheers,
=David
On Jun 9, 2009, at 2:06 PM, David Leangen wrote:
Ok, this seems to have something to do with proxying, not Wicket.
When I enter 日本語 into the form,