Re: Problems with UTF-8 chars in query string
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, 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 /path/?q=%25E6%2597%25A5%25E6%259C%25AC%25E8%25AA%259E HTTP/1.1 The second request is double-encoded and is not correct. So, not a Wicket problem. However, any ideas where I could look for the solution? Thanks! =David On Jun 9, 2009, at 1:56 PM, David Leangen wrote: 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 in my browser, there are no problems. If I use the form, then the value gets double encoded. If I access the machine directly, there is no problem, even from within the form. If I access the machine externally via my proxy, then the double encoding occurs. So, I am not able to reproduce the problem since it is only on my production machine. I have been using a remote debugger to step through the code to try to figure this out, but have so far been unsuccessful. I noticed this issue: https://issues.apache.org/jira/browse/WICKET-1627 But I am using v 1.3.5, so this should not be a problem. Thank you! =David - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Problems with UTF-8 chars in query string
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 /path/?q=%25E6%2597%25A5%25E6%259C%25AC%25E8%25AA%259E HTTP/1.1 The second request is double-encoded and is not correct. So, not a Wicket problem. However, any ideas where I could look for the solution? Thanks! =David On Jun 9, 2009, at 1:56 PM, David Leangen wrote: 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 in my browser, there are no problems. If I use the form, then the value gets double encoded. If I access the machine directly, there is no problem, even from within the form. If I access the machine externally via my proxy, then the double encoding occurs. So, I am not able to reproduce the problem since it is only on my production machine. I have been using a remote debugger to step through the code to try to figure this out, but have so far been unsuccessful. I noticed this issue: https://issues.apache.org/jira/browse/WICKET-1627 But I am using v 1.3.5, so this should not be a problem. Thank you! =David - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Problems with UTF-8 chars in query string
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 in my browser, there are no problems. If I use the form, then the value gets double encoded. If I access the machine directly, there is no problem, even from within the form. If I access the machine externally via my proxy, then the double encoding occurs. So, I am not able to reproduce the problem since it is only on my production machine. I have been using a remote debugger to step through the code to try to figure this out, but have so far been unsuccessful. I noticed this issue: https://issues.apache.org/jira/browse/WICKET-1627 But I am using v 1.3.5, so this should not be a problem. Thank you! =David - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
