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

[request]: Support Redirection #74

Open
SleeperSmith opened this issue May 29, 2019 · 3 comments
Open

[request]: Support Redirection #74

SleeperSmith opened this issue May 29, 2019 · 3 comments
Assignees
Labels
Roadmap: Accepted We are planning on doing this work.

Comments

@SleeperSmith
Copy link

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

@SleeperSmith SleeperSmith added the Roadmap: Proposed We are considering this for inclusion in the roadmap. label May 29, 2019
@melo
Copy link

melo commented May 29, 2019

Just to understand something from your setup: if you have nginx as the inbound proxy, can’t you use that for the redirects?

@dastbe
Copy link
Contributor

dastbe commented May 29, 2019

Hey @SleeperSmith

  1. Does the redirect need to be visible to the application itself, or are you interested in having the redirect occur transparently within Envoy.
  2. Do you want to define the redirect operation in App Mesh itself, or do you want to respect redirects that come from the upstream destination?

@SleeperSmith
Copy link
Author

SleeperSmith commented May 30, 2019

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.

@melo

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.

@dastbe

  1. I need the redirect to be visible to the application is self. In this case, the Nginx, which will serve back the redirect.
  2. I need the redirect operation to be defined in the App Mesh itself. Redirects from upstream already work currently.

@shubharao shubharao added Roadmap: Accepted We are planning on doing this work. and removed Roadmap: Proposed We are considering this for inclusion in the roadmap. labels Sep 27, 2019
@shubharao shubharao self-assigned this Sep 27, 2019
@herrhound herrhound assigned herrhound and unassigned shubharao Apr 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Roadmap: Accepted We are planning on doing this work.
Projects
None yet
Development

No branches or pull requests

5 participants