Skip to content
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

replacePrefixMatch broken in main #4331

Open
zetaab opened this issue Sep 25, 2024 · 7 comments
Open

replacePrefixMatch broken in main #4331

zetaab opened this issue Sep 25, 2024 · 7 comments
Labels
Milestone

Comments

@zetaab
Copy link
Contributor

zetaab commented Sep 25, 2024

Description:

What issue is being seen? Describe what should be happening instead of
the bug, for example: Envoy should not crash, the expected value isn't
returned, etc.

with envoy gateway 1.1 I was using following spec

    - type: URLRewrite
      urlRewrite:
        path:
          type: ReplacePrefixMatch
          replacePrefixMatch: /docs/

So my goal is to add /docs/ prefix to all url paths. So it will be modified like /docs/<originalpath>.

With latest main the request path was modified only /docs<originalpath> (NOTE! missing last slash)

However, with latest main it will not add the ending slash anymore. I was forced to use

    - type: URLRewrite
      urlRewrite:
        path:
          type: ReplacePrefixMatch
          replacePrefixMatch: /docs//

to get same behaviour working.

Repro steps:

Include sample requests, environment, etc. All data and inputs
required to reproduce the bug.

Note: If there are privacy concerns, sanitize the data prior to
sharing.

Environment:

Include the environment like gateway version, envoy version and so on.

eg 1.1 (envoy 1.31) and main (with envoy distroless-devel)

Logs:

Include the access logs and the Envoy logs.

@zetaab zetaab added the triage label Sep 25, 2024
@arkodg
Copy link
Contributor

arkodg commented Sep 25, 2024

this was supposed to be fixed with #3990

Copy link

This issue has been automatically marked as stale because it has not had activity in the last 30 days.

@github-actions github-actions bot added the stale label Oct 26, 2024
@zirain
Copy link
Contributor

zirain commented Oct 26, 2024

@arkodg do we have e2e for this now?

@arkodg arkodg added this to the v1.2.0 milestone Oct 26, 2024
@arkodg arkodg removed the stale label Oct 26, 2024
@arkodg
Copy link
Contributor

arkodg commented Oct 26, 2024

@arkodg do we have e2e for this now?

I dont think so, added this to v1.2.0 so we can add something and ensure there's no regression

@arkodg arkodg modified the milestones: v1.2.0, Backlog Nov 6, 2024
@zetaab
Copy link
Contributor Author

zetaab commented Nov 13, 2024

now this exists in 1.2.1 release.

Copy link

This issue has been automatically marked as stale because it has not had activity in the last 30 days.

@github-actions github-actions bot added the stale label Dec 13, 2024
@zetaab
Copy link
Contributor Author

zetaab commented Dec 14, 2024

still valid

@github-actions github-actions bot removed the stale label Dec 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants