User reports difficulty setting up redirects in Emissary 2.0
See original GitHub issueFrom user Tim Rice:
Hi! Trying out the emissary-ingress 2.0 dev preview… having trouble getting redirects working, even using the basic redirect example from the docs
apiVersion: x.getambassador.io/v3alpha1
kind: AmbassadorMapping
metadata:
name: redirect
spec:
prefix: /redirect/
service: httpbin.org
host_redirect: true
hostname: ‘*’
just returns a 404. accessing an application in the cluster works just fine… is this a known problem or are we doing something wrong?
Comment from Cindy: The user is reporting an issue with redirects for Emissary 2.0 and it seems like he’s using the new CRDs… he says it works for 1.13.
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (2 by maintainers)
Top Results From Across the Web
Emissary-ingress Release Notes | Ambassador
By default Emissary-ingress adds routes for http to https redirection. When an AuthService is applied in v2.Y of Emissary-ingress, Envoy would skip the ......
Read more >Support global level http -> https redirection · Issue #469
Use Case If TLS terminates externally (Such as AWS ELB), the http request need to be redirected to https. Describe the solution you'd...
Read more >Solving Redirection Issues Using Rank Math SEO Plugin
To solve this problem, open the redirects and see if you could find any redirects that have the same source and destination URLs....
Read more >Redirect Users to Your Experience Builder Site Pages
Set up page redirects to maintain the discoverability and SEO equity of your Experience Builder site. You can redirect users to your Experience...
Read more >The Ultimate Guide to Redirects: URL Redirections Explained
Redirects send users & search engines from one URL to another. Find out how to use each type here.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This was fixed in Emissary-ingresss 2.1.2, which is now available.
@vjdhama can you explain how you used
externalName
mapping to resolve your redirect problem? I created anexternalName
service and pointed the redirect mapping to that but still get the404
error.The bugfix looks like it will be in 2.1.2, anyone have an idea on the timeframe for that release?