"Johan Compagner" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > do you still have that problem in 1.1?
No, it is fixed, but I am talking about different problem :-) When browser sends back form parameters, it will encode them with the same encoding as the page. When the page is encoded in utf-8, the parameters sent back will be in utf-8. But the used encoding is not part of the POST/GET query, so the server has no change to guess them and uses default encoding, which is not utf-8. In ideal world the server should remember the encoding of the page, but HTML protocol is stateless. The filter I posted corrects the problem. Jan ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
