I have couple of questions:
1. Why there is the redirect? Why one more client-server round trip?
This redirect is the default redirect strategy that we use
You can set yours if you want to something different see
ApplicationSettings RenderingStrategy
We use default the REDIRECT_TO_BUFFER
This has some advantages and you don't get that post message back when
you refresh the page
2. Why the resulting page has wrong encoding? (The content type is utf-8,
but the generated content is not utf-8).
Then it seems that the browser doesn't send the right headers with that
response in what type of encoding it wants it??
when it is responding to the redirect request? Can you check this with a
sniffer?
Or does a servlet container response with the same encoding the browser
sends something.
But then all redirects could be gone bad because what does the browser
send then?
johan
-------------------------------------------------------
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
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
