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

[JWS] Enable RemoteIPValve by default

XMLWordPrintable

    • 1
    • Hide
      Cause: RemoteIpValve not included in server.xml
      Consequence: X-Forwarded-* headers not available to AccessLogValve
      Fix: Added RemoteIpValve to server.xml
      Result: X-Forwarded-* headers available to AccessLogValve
      Show
      Cause: RemoteIpValve not included in server.xml Consequence: X-Forwarded-* headers not available to AccessLogValve Fix: Added RemoteIpValve to server.xml Result: X-Forwarded-* headers available to AccessLogValve
    • CLOUD Maintenance Sprint 11

      registry.access.redhat.com/jboss-webserver-3/webserver30-tomcat7-openshift:1.2-31

      Currently this is not configured and HttpServletRequest.getRemoteHost() returns router address instead of client IP address. It would be great if it's configured by default and reflect X_Forwarded_For value to this API. Also it would be nice if we have a switch to disable RemoteIPValve installation for migrated apps that already proxy aware and read X_Forwarded_For header directly.

      In OpenShift 2 RemoteIPValve was configured by default:

              <Valve
          className="org.apache.catalina.valves.RemoteIpValve"
          protocolHeader="x-forwarded-proto"
        />

              wdecoste1@redhat.com William Decoste (Inactive)
              rhn-support-tkimura Takayoshi Kimura
              Libor Fuka Libor Fuka
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: