Re: about webshere and relative url redirects: https://issues.apache.org/jira/browse/WICKET-3258
2012/2/7 Dominik Drzewiecki dominik.drzewie...@gmail.com: 2012/2/6 Johan Compagner jcompag...@gmail.com: 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? Will give you complete details as soon as I gather them when I get to the office. There might have been something that relates to your particular case My Web Container custom properties (followed by value, IBM issue id and url): AlwaysEncodeUrl false PM18198 http://www-01.ibm.com/support/docview.wss?rs=180uid=swg1PM18198 com.ibm.ws.webcontainer.httpOnlyCookies JSESSIONID PK98436 http://www-01.ibm.com/support/docview.wss?uid=swg1PK98436 com.ibm.ws.webcontainer.invokeFiltersCompatibility true PK69491 http://www-01.ibm.com/support/docview.wss?uid=swg1PK69491 com.ibm.ws.webcontainer.mapFiltersToAsterisk true PK57083 http://www-01.ibm.com/support/docview.wss?rs=180uid=swg1PK57083 com.ibm.ws.webcontainer.removetrailingservletpathslash true PK39337 http://www-01.ibm.com/support/docview.wss?uid=swg1PK39337 Problems I've been struggling with (reported several of them): http://www-01.ibm.com/support/docview.wss?uid=swg1PK98436 http://www-01.ibm.com/support/docview.wss?uid=swg24014758 http://www-01.ibm.com/support/docview.wss?rs=180uid=swg1PK57083 http://www-01.ibm.com/support/docview.wss?uid=swg1PK39337 http://www-01.ibm.com/support/docview.wss?rs=180uid=swg1PK85015 http://www-01.ibm.com/support/docview.wss?uid=swg1PK69491 http://www-01.ibm.com/support/docview.wss?rs=180uid=swg1PM18198 You should particularly take a peek at PK39337. These however relate to was 6.1, but those bugs might still exist in 8.0. I have a feeling that the Big Blue tend not to retrofit fixes. HTH regz, /dd -- /* Spelin donut mader if iz ina coment */
Re: about webshere and relative url redirects: https://issues.apache.org/jira/browse/WICKET-3258
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.comwrote: 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??
Re: about webshere and relative url redirects: https://issues.apache.org/jira/browse/WICKET-3258
Hi Johan, I think you can reproduce the same behavior with simple Servlet and HttpServletResponse.sendRedirect(). If it still breaks then it is something to tune in WebSphere. If it works then there is something in Wicket. On Mon, Feb 6, 2012 at 6:06 PM, 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?? -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com
Re: about webshere and relative url redirects: https://issues.apache.org/jira/browse/WICKET-3258
In wicket you can work around it (see the doc of WebResponse.sendRedirect()) I have currently no idea if you tune this behavior in websphere, i am just testing it a bit to see if it would possible work in websphere (but i encounter more problems that just this, for example getPathInfo() and getServletPath() and so on also behaves differently then in other containers. On Tue, Feb 7, 2012 at 09:15, Martin Grigorov mgrigo...@apache.org wrote: Hi Johan, I think you can reproduce the same behavior with simple Servlet and HttpServletResponse.sendRedirect(). If it still breaks then it is something to tune in WebSphere. If it works then there is something in Wicket. On Mon, Feb 6, 2012 at 6:06 PM, 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?? -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com
about webshere and relative url redirects: https://issues.apache.org/jira/browse/WICKET-3258
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??
Re: about webshere and relative url redirects: https://issues.apache.org/jira/browse/WICKET-3258
2012/2/6 Johan Compagner jcompag...@gmail.com: 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? I have been struggling with Websphere 6.1 for quite some time, and eventually sorted out the glitches and made it run wicket apps smoothly. There have been several so called custom properties to be set and several patches to be applied (which eventally ended up being part of FPs). Will give you complete details as soon as I gather them when I get to the office. There might have been something that relates to your particular case I thought it was only the company I work for that uses crappy WebSphere ;) and everyone else use decent application servers. regz, /dd -- /* Spelin donut mader if iz ina coment */
