docs: requestHeaderPolicy example in Request Rewriting documentation #6805
Labels
kind/bug
Categorizes issue or PR as related to a bug.
lifecycle/needs-triage
Indicates that an issue needs to be triaged by a project contributor.
What steps did you take and what happened:
I found a potentially incorrect YAML example in the documentation at https://projectcontour.io/docs/main/config/request-rewriting/#manipulating-the-host-header
The current example shows
requestHeaderPolicy
as a separate route element:What did you expect to happen:
I believe requestHeaderPolicy should be part of the same route element, not a separate one. The correct YAML should be:
Here's the diff showing the change:
The current example would likely not work as intended because it shows requestHeaderPolicy as a separate route element without any conditions or services. While this might be valid YAML syntax, it would not achieve the expected header rewriting behavior.
Anything else you would like to add:
host
header on HTTPProxy routes. #5678Could you please confirm if this is indeed a documentation error? If my understanding is correct, the current example might be misleading for users.
Environment:
N/A (Documentation issue)
The text was updated successfully, but these errors were encountered: