Johan (and others), I just noticed this thread (and then noticed that you cc'd me). I never have actually run websphere for any of my applications. I was on-site at a client and they had this problem. We dug through it, I committed that extension point and then immediately wiped it from my memory :)
This commit didn't actually "fix" anything for this situation. It simply gave the client a way that they could override sendRedirect. IIRC they overrode it and converted URLs from relative to absolute before passing the redirect off to the servlet response. They had tons of app-specific URL-handling code, but the same idea should work for anyone (I think). HTH -- Jeremy Thomerson http://wickettraining.com *Need a CMS for Wicket? Use Brix! http://brixcms.org* On Mon, Feb 6, 2012 at 11:06 AM, Johan Compagner <jcompag...@gmail.com>wrote: > Websphere, > > i am currently testing our product in a war deployment with the latest > wicket 1.4 code > But i am still bumping against this with Websphere 8.0.2 > > was it really fixed? Do i need a setting somehow? > > It is really weird for example > > if this is the url > > http://jcompagner-pc:9080/servoy/servoy-webclient/solutions/solution/RadioTest > > we send > > ../../?wicketurl > > which is correct because we should get: > > http://jcompagner-pc:9080/servoy/servoy-webclient/?wicketurl > > but what i get: > > http://jcompagner-pc:9080/?wicketurl > > weird thing is if i do this: > > > http://jcompagner-pc:9080/servoy/servoy-webclient/solutions/solution/RadioTest/a/b > > we send: > > ../../../../?wicketurl > > and then it works! > > But if i then play with it a bit > > > http://jcompagner-pc:9080/servoy/servoy-webclient/solutions/solution/RadioTest/a/b > > and then force that this is send: > > ../../../?wicketurl > > > i get: > > http://jcompagner-pc:9080/servoy/servoy-webclient/solutions/?wicketurl > > so that is still correct, there is 1 less removed.. > But now i remove another one: > > ../../?wicketurl > > then i get this: > > http://jcompagner-pc:9080/?wicketurl > > ??? > so now it seems to only use the servlet path/context again! > > if i kill another: > > ../?wicketurl > > http://jcompagner-pc:9080/servoy/?wicketurl > > so it seems that if the relative url has context/servletpath up dirs (so 1 > or 2 ../) then it sees it as the context/servletpath thing > and if it is more so i have 3 times ../ it sees it as the whole url!! > > Is Websphere trying to be to smart?? >
