setResponsePage redirects to wrong url
When I do setResponsePage(MyHomePage.class) IE tries to show me "my.site.com/./" url and gets 404 response. Firefox just shows "my.site.com" without any troubles. I'm using wicket 1.3-beta2 and WicketFilter mapped to /*. Is it a known bug? Is there a workaround? -- Andrew Klochkov - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: setResponsePage redirects to wrong url
Andrew Klochkov wrote: > When I do setResponsePage(MyHomePage.class) IE tries to show me > "my.site.com/./" url and gets 404 response. Firefox just shows > "my.site.com" without any troubles. > > I'm using wicket 1.3-beta2 and WicketFilter mapped to /*. > > Is it a known bug? Is there a workaround? > I managed to reproduce it in a quickstart project so I'm sure it's a bug. BTW it's being reproduced under tomcat only, jetty works fine. My tomcat version is 5.5.17. -- Andrew Klochkov - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: setResponsePage redirects to wrong url
Andrew Klochkov wrote: Andrew Klochkov wrote: When I do setResponsePage(MyHomePage.class) IE tries to show me "my.site.com/./" url and gets 404 response. Firefox just shows "my.site.com" without any troubles. I'm using wicket 1.3-beta2 and WicketFilter mapped to /*. Is it a known bug? Is there a workaround? I managed to reproduce it in a quickstart project so I'm sure it's a bug. BTW it's being reproduced under tomcat only, jetty works fine. My tomcat version is 5.5.17. Please can you submit this to JIRA? Regards, Al - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: setResponsePage redirects to wrong url
Al Maw wrote: > Andrew Klochkov wrote: >> Andrew Klochkov wrote: >>> When I do setResponsePage(MyHomePage.class) IE tries to show me >>> "my.site.com/./" url and gets 404 response. Firefox just shows >>> "my.site.com" without any troubles. >>> >>> I'm using wicket 1.3-beta2 and WicketFilter mapped to /*. >>> >>> Is it a known bug? Is there a workaround? >>> >> I managed to reproduce it in a quickstart project so I'm sure it's a >> bug. >> BTW it's being reproduced under tomcat only, jetty works fine. My tomcat >> version is 5.5.17. >> > > Please can you submit this to JIRA? > https://issues.apache.org/jira/browse/WICKET-847 -- Andrew Klochkov - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
