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

Logging filter ignores X-Forwarded-For request header

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Medium
    • Resolution: Fixed
    • Affects Version/s: 2.11.2, 2.12-RC1
    • Fix Version/s: 2.11.3, 2.12.0
    • Component/s: Main
    • Labels:
      None

      Description

      The logging filter does not check for the X-Forwarded-For request header when logging the client address. This causes the logging filter to log the address of the proxy server when deploying GeoServer in a WildFly application server and using a proxy. Several GeoServer extensions that use the client address (Control Flow, GeoFence and Monitoring) all use nearly identical code to extract the first address in the X-Forwarded-For header if it is present.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              sikeoka Steve Ikeoka
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: