]
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:
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.