State of X-Forwarded-Host header

[barchw]

Description
In the current v1beta1 version, the singular Host field is used to fill in the X-Forwarded-Host http header. APIRule v2alpha1 will introduce support for matching on multiple Hosts. This influences logic of how to set this value, as it is not possible to be sure that the client request always requested the same Host.

As result of the above, there is a need to evaluate the support for this header. If possible, the aim should be to dynamically fill in the value, for example by utilisation of (if such feature is present) Envoy/Istio feature.

If it will not be possible to ensure that this value is dynamically filled in, the next step should be evaluation of the support for this header.

Reasons

• Introduction of APIRule v2alpha1

DoD:

• Provide unit and integration tests.
• Provide documentation.
• Verify if the solution works for both open-source Kyma and SAP BTP, Kyma runtime.
• If you changed the resource limits, explain why it was needed.
• Verify that your contributions don't decrease code coverage. If they do, explain why this is the case.
• Add release notes.

Attachments