Hi,
There is something in your code.
Wicket generates relative paths for the redirects and the port is not
touched at all.
The port is touched only if HttpsMapper is used.
If you think it is problem in Wicket then create a quickstart app that
reproduces the problem and attach it to Jira.
On Thu, Mar 15, 2012 at 5:15 PM, relong <topdog...@hotmail.com> wrote:
> All,
>
> In Wicket 1.5.4, when I have a redirect using setResponsePage() on my test
> Jetty server, the URL changes from localhost:8080/myapp to localhost/myapp,
> which breaks things, obviously.
>
> Here's a code snippet as an example of redirection:
>
> In my Login.class file:
>
> public void onSubmit(){
> Â <doing stuff, like checking LDAP for login credentials...>
>
> Â RequestCycle.get().setResponsePage(new
> RequestForm(username.getModelObject()));
> }
>
> Any reason why it removes the port from the URL? It didn't do this in
> 1.4.19. How should I fix this for 1.5?
>
> Thanks!
>
>
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/Wicket-1-5-4-setResponsesPage-removing-port-from-URL-tp4475303p4475303.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
