-
Notifications
You must be signed in to change notification settings - Fork 24
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
[request]: Support Redirection #74
Comments
Just to understand something from your setup: if you have nginx as the inbound proxy, can’t you use that for the redirects? |
Hey @SleeperSmith
|
Just FYI, I am putting App Mesh to this use only because it seems like something can work in terms of its mechanics, and that these functionality are supported by upstream Envoy. I can understand if App Mesh (currently) does not have a design goal to be an ingress controller for web/browser traffic and to support these associated functionality. Let me know. We are looking to allow redirect hijacking of paths to be more dynamically managed. Like managed by a content / marketing team etc. Updating the nginx config would mean having to update any one of Docker image / Launch Configuration (to modify the nginx config). It requires code commit / deployment etc.
|
Tell us about your request
Support redirect action
https://www.envoyproxy.io/docs/envoy/latest/api-v2/api/v2/route/route.proto#route-redirectaction
Which integration(s) is this request for?
ECS / Service Discovery
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
We have a website.com served through:
nginx -> mesh -> website.com server
We want to be able to do redirect on arbitrary paths (through the router).
website.com/redirect-to-something -> redirect to something.com/
Are you currently working around this issue?
We forward the traffic to a redirect service EasyRedir.com and serve the redirect response from there.
Additional context
Attachments
The text was updated successfully, but these errors were encountered: