-
Notifications
You must be signed in to change notification settings - Fork 668
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support Host header rewrites per-service #4002
Comments
seems nice to have, tagging it v1.20 tentatively |
Hi, I would like to work on this feature if it is still unassigned. Can someone assign it to me? |
assigned @adnanhb, let us know if you have any questions about how to proceed! |
@adnanhb are you still working on this? let us know if you need anything from us or if we should reassign this issue |
Sunjay, i have completed the implementation, just need to get around to testing it. I will revert back with a PR soon. |
The latter does not allow the |
Updates projectcontour#4002 Signed-off-by: Fang Peng <fpeng@vmware.com>
Closes #4002 Signed-off-by: Fang Peng <fpeng@vmware.com>
) Closes projectcontour#4002 Signed-off-by: Fang Peng <fpeng@vmware.com>
) Closes projectcontour#4002 Signed-off-by: Fang Peng <fpeng@vmware.com> Signed-off-by: yy <yang.yang@daocloud.io>
Currently, Contour supports rewriting the
Host
header at the route level only. It's explicitly disallowed at the per-service level, because Envoy did not historically support it. As of Envoy 1.19.0, however, settinghost_rewrite_literal
for an individual weighted cluster is now supported (see https://www.envoyproxy.io/docs/envoy/v1.19.0/version_history/current#new-features), so Contour should expose this functionality.The text was updated successfully, but these errors were encountered: