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

Envoy config - Follow Redirect #2846

Open
lduparc opened this issue Jul 2, 2020 · 1 comment
Open

Envoy config - Follow Redirect #2846

lduparc opened this issue Jul 2, 2020 · 1 comment
Labels
stale Issue is stale and will be closed t:feature New feature or enhancement request

Comments

@lduparc
Copy link

lduparc commented Jul 2, 2020

At the moment, there is no way to configure Ambassador to follow redirects.
This is a big constraint if we work with historical apps/apis which supposed that the redirect will be followed and if we cannot update code to manage this case.

Could you please support for this ?

Checking envoy documentation It is configurable in with the internal_redirect_policy configuration in Envoy https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/route/v3/route_components.proto#envoy-v3-api-field-config-route-v3-routeaction-internal-redirect-policy

@stale
Copy link

stale bot commented Aug 31, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale Issue is stale and will be closed label Aug 31, 2020
@LukeShu LukeShu removed the stale Issue is stale and will be closed label Jun 8, 2022
@cindymullins-dw cindymullins-dw added the t:feature New feature or enhancement request label Oct 27, 2022
@dosubot dosubot bot added the stale Issue is stale and will be closed label Jul 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Issue is stale and will be closed t:feature New feature or enhancement request
Projects
None yet
Development

No branches or pull requests

3 participants