Wicket
  1. Wicket
  2. WICKET-3885

setResponsePage in AjaxLink goes always to localhost:8080 instead to the right host and port

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.5-RC5.1
    • Fix Version/s: 1.5-RC6
    • Component/s: wicket
    • Labels:
      None

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

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Martin Grigorov
            Reporter:
            Alain Sillen
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development