-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
the upstream receive // path #26055
Comments
CC @yanavlasov , seems reasonable to make rewrites produce valid paths. |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". Thank you for your contributions. |
@kyessenov This issue auto closed ptal and label with |
As far as I'm aware this issue wasn't fixed, but it seems pretty fundamental for routing. Are there any plans to support this features? |
I will work on this issue/bug. |
like envoy doc configured, use
pathSeparatedPrefix
and pre_rewrite is "/":the
pathSeparatedPrefix
"/om/backend" would watchreference envoy docs:
but the upstream receive double "/"
the pre_rewrite is not "/" work fine:
I think we should trim the double "/" when the prefix_write is "/" and the prefix is
pathSeparatedPrefix
.The text was updated successfully, but these errors were encountered: