You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2011/07/12 12:11:00 UTC

[jira] [Resolved] (WICKET-3885) setResponsePage in AjaxLink goes always to localhost:8080 instead to the right host and port

     [ https://issues.apache.org/jira/browse/WICKET-3885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Grigorov resolved WICKET-3885.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.5-RC6

> setResponsePage in AjaxLink goes always to localhost:8080 instead to the right host and port
> --------------------------------------------------------------------------------------------
>
>                 Key: WICKET-3885
>                 URL: https://issues.apache.org/jira/browse/WICKET-3885
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-core
>    Affects Versions: 1.5-RC5.1
>            Reporter: Alain Sillen
>            Assignee: Martin Grigorov
>             Fix For: 1.5-RC6
>
>
> setResponsePage in an AjaxLink in Wicket 1.4 redirects with a relative path to the response page.
> Wicket 1.5 takes the absolute path "localhost:8080/path to the response page" even when the host and port are different.
> (e.g. with Apache2 a virtual host is created with server name www.mycompany.com, setResponce wil go to "localhost:8080/path to page" instead of  "www.mycompany.com/path to page")

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira