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

RequestRedirect filter on HTTPRoute cannot preserve path in request #6557

Open
2 of 4 tasks
randmonkey opened this issue Oct 22, 2024 · 0 comments
Open
2 of 4 tasks
Labels
area/feature New feature or request area/gateway-api Relating to upstream Kubernetes SIG Networking Gateway API

Comments

@randmonkey
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Does this enhancement require public documentation?

  • I have added an Acceptance Criteria item for adding and/or adjusting public documentation (if applicable)

Problem Statement

From FTI-6305.
Because the RequestRedirect filter is implemented by request-termination and response-transformer plugin. This cannot include variable part in the response head. So the redirect path in the response body is fixed and cannot preserve path in the request.

Proposed Solution

  • Use some other method to generate redirect response that can send variable response according to the request
    • For example: run a standalone server to send responses

Additional information

No response

Acceptance Criteria

  • Redirect path in the response header can be preserved if no path is given
  • ReplacePrefixMatch is also supported
@randmonkey randmonkey added area/feature New feature or request area/gateway-api Relating to upstream Kubernetes SIG Networking Gateway API labels Oct 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/feature New feature or request area/gateway-api Relating to upstream Kubernetes SIG Networking Gateway API
Projects
None yet
Development

No branches or pull requests

1 participant