|
|
Steve Ikeoka created an issue |
|
Issue Type: |
|
|---|---|
|
Affects Versions: |
2.11.2, 2.12-RC1 |
|
Assignee: |
Unassigned |
|
Components: |
Main |
|
Created: |
04/Oct/17 6:40 PM |
|
Priority: |
|
|
Reporter: |
|
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. |
|
|
|
Get JIRA notifications on your phone! Download the JIRA Cloud app for Android or iOS |
|
|
This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100063-sha1:bdf8149) |
|
|
|