Uploaded image for project: 'GeoServer'
  1. GEOS-7526

Hazelcast/JDBConfig clustering issues caused by HTTP 302 response and unique wicket resource IDs

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Medium
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.9.1, 2.10-M0
    • Component/s: Community modules
    • Labels:
      None

      Description

      Trying out 2.9 Beta2 with Hazelcast clustering I noticed that every UI request results with an HTTP 302 response and a unique ID appended to the URL.
      when using a single instance this isn't that big of an issue, however when having multiple instances behind a load balancer this results with multiple redirects, which causes the UI to be unusable.(In most cases the browser will just give up).
      In some cases this can also become an issue with a single instance behind a proxy.

      Looking around I wasn't able to find the commit that added that change, but I'm guessing this was done as part of the wicket upgrade.

      Anyone knows if this was this was done in response to a specific issue, or just as an artifact of the wicket upgrade?
      Would it be possible to change this behavior back to something that resembles 2.8 (eg HTTP 200 and non unique IDs)?

      Thanks,
      Ami.

        Attachments

          Activity

            People

            • Assignee:
              NielsCharlier Niels Charlier
              Reporter:
              NielsCharlier Niels Charlier
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: