Uploaded image for project: 'Cloud Enablement'
  1. Cloud Enablement
  2. CLOUD-1820

StdoutAccessLogValve should also log X-Forwarded-For header

    Details

    • Target Release:
    • Story Points:
      1
    • Affects:
      Release Notes
    • Release Notes Text:
      Hide
      Feature: X-Forward-Host header has been added to the log pattern
      Reason: The OpenShift HAProxy router adds X-Forward-Host header to the proxied requests with the original hostname of the request.
      Result: The original HTTP request hostname is now visible in the access log
      Show
      Feature: X-Forward-Host header has been added to the log pattern Reason: The OpenShift HAProxy router adds X-Forward-Host header to the proxied requests with the original hostname of the request. Result: The original HTTP request hostname is now visible in the access log
    • Sprint:
      CLOUD Maintenance Sprint 9

      Description

      The access log does not contain the original host doing the request if the request goes thorugh the haproxy. Only the haproxy IP address is visible in the access log

      11:35:32,027 INFO [org.jboss.openshift.valves.StdoutAccessLogValve] (http-0.0.0.0:8080-1) 10.1.0.1 - - [20/Jun/2017:11:35:31 +0000] "GET /kie-server/services/rest/server HTTP/1.1" 401 996

      It might be useful to also print the X-Forwarded-For header, so that the original IP address is logged.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  bdecoste William Decoste
                  Reporter:
                  maschmid Marek Schmidt
                  Tester:
                  Marek Schmidt
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  6 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: