diff --git a/undertow/WFLY-14255_Make_resuseXForwarded_and_rewriteHost_configurable.adoc b/undertow/WFLY-14255_Make_resuseXForwarded_and_rewriteHost_configurable.adoc new file mode 100644 index 000000000..d9f0958b1 --- /dev/null +++ b/undertow/WFLY-14255_Make_resuseXForwarded_and_rewriteHost_configurable.adoc @@ -0,0 +1,116 @@ += Make ReuseXForwarded and RewriteHost configurable +:author: Bartosz Baranowski +:email: bbaranow@redhat.com +:toc: left +:icons: font +:idprefix: +:idseparator: - + +== Overview + +In some scenarios it is a requirement to reuse x forwarded or rewrite host header. Currently ProxyHandler flags controlling both are hardcoded to 'false', meaning mentioned functionality is not accessible. +This RFE adress this by introduction of model values that control mentioned flags. + +== Issue Metadata + +=== Issue + +* https://issues.redhat.com/browse/WFLY[WFLY-14255] + +=== Related Issues + + +=== Dev Contacts + +* mailto:{email}[{author}] + +=== QE Contacts + +* mailto:msvehla@redhat.com[Martin Svehla] + +=== Testing By +// Put an x in the relevant field to indicate if testing will be done by Engineering or QE. +// Discuss with QE during the Kickoff state to decide this +* [ ] Engineering + +* [x] QE + +=== Affected Projects or Components + +* Web/Undertow + +=== Other Interested Projects + +=== Relevant Installation Types +// Remove the x next to the relevant field if the feature in question is not relevant +// to that kind of WildFly installation +* [x] Traditional standalone server (unzipped or provisioned by Galleon) + +* [x] Managed domain + +* [x] OpenShift s2i + +* [x] Bootable jar + +== Requirements + +=== Hard Requirements + +* Being able to configure both flags via model. + +=== Nice-to-Have Requirements + +=== Non-Requirements + +== Backwards Compatibility + +Subsystem transformers should be able to handle it. + +=== Default Configuration +[literal] + + .... + + + + + + .... + + +=== Importing Existing Configuration + +No steps, transformers should handle purging default value for previous configs. + + +=== Deployments + +No. Default is still false for both, so there should be no change in behavior. + +=== Interoperability + +Not affected. + +== Security Considerations + +//// +Identification if any security implications that may need to be considered with this feature +or a confirmation that there are no security implications to consider. +//// + +== Test Plan + +== Community Documentation + +Should be part of model reference. + +== Release Note Content +//// +Draft verbiage for up to a few sentences on the feature for inclusion in the +Release Note blog article for the release that first includes this feature. +Example article: http://wildfly.org/news/2018/08/30/WildFly14-Final-Released/. +This content will be edited, so there is no need to make it perfect or discuss +what release it appears in. "See Overview" is acceptable if the overview is +suitable. For simple features best covered as an item in a bullet-point list +of features containing a few words on each, use "Bullet point: " +////