Hello,

Could you please explain for what reason wicket for every page redirects
users to some other page by 302 code?
For example from /home user will be redirected to /home?1 etc.
It seems quite strange and I think, that this is much more strange for
Search Engines.
I found solution how to optimize for SE here:
http://apache-wicket.1842946.n4.nabble.com/Removing-jsessionid-in-wicket-1-5-td3891735.html
But it looks strange even for common users. Can I disable "this feature" for
common users?

P.S. I found some mentions that this is because page is not stateless. But
it's not so reasonable for me, because:
1) In wicket 1.4 all works great without this "feature"
2) Other web frameworks, which I know, don't use 302 code and everthing is
working
For me it looks as a bug.

Thanks,

Ilia

Reply via email to