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

["Alain Sillen (JIRA)" <ji...@apache.org>]

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

Alain Sillen updated WICKET-3885:
---------------------------------

    Description: 
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")

  was:
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.


> 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
>
> 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