[jboss-jira] [JBoss JIRA] (WFLY-9781) Support Forwarded HTTP Extension - RFC 7239

[Stuart Douglas (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-9781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stuart Douglas moved EAP7-906 to WFLY-9781:
-------------------------------------------

               Project: WildFly  (was: EAP 7 Planning Pilot)
                   Key: WFLY-9781  (was: EAP7-906)
            Issue Type: Feature Request  (was: Requirement)
              Workflow: GIT Pull Request workflow   (was: EAP Agile Workflow 1.2)
           Component/s: Web (Undertow)
                            (was: Undertow)
    Polarion Test Plan:   (was: https://polarion.engineering.redhat.com/polarion/#/project/EAP7/wiki/RFEs_7_2/EAP7-834)
     Analysis Document:   (was: https://github.com/wildfly/wildfly-proposals/pull/5)


> Support Forwarded HTTP Extension - RFC 7239
> -------------------------------------------
>
>                 Key: WFLY-9781
>                 URL: https://issues.jboss.org/browse/WFLY-9781
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: Web (Undertow)
>            Reporter: Stuart Douglas
>            Assignee: Stuart Douglas
>              Labels: tp_candidate
>
> "X-Forwarded-For, X-Forwarded-By, and  X-Forwarded-Proto" headers are non-standards headers and implementations might vary in different environments.
> RFC-7239 standardizes a header field called "Forwarded" and provides the syntax and semantics for disclosing such information. I see that now a days most of the vendors supporting this including routes in "Openshift container platform" but due to lack of support in Undertow limiting us to relay on X-Forwarded-For* headers.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)