Wicket
  1. Wicket
  2. WICKET-4824

Redirect to HTTPS is using wrong port 80 if HttpsConfig with default ports 80/443 is used

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 6.1.1
    • Fix Version/s: 6.2.0
    • Component/s: wicket
    • Labels:
      None

      Description

      HttpsMapper#mapHandler() doesn't set the Url's port, if the desired protocol uses the standard port.

      This leads to UrlRenderer choosing to the request's port as fallback (which is 80 before switching to https).

        Activity

        Hide
        Sven Meier added a comment -

        Port is now always set explicitly, it won't be rendered by UrlRenderer if not required

        Show
        Sven Meier added a comment - Port is now always set explicitly, it won't be rendered by UrlRenderer if not required

          People

          • Assignee:
            Sven Meier
            Reporter:
            Sven Meier
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development