You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey @e33ivanyauwai, I think I'm having trouble understanding the redirects in your example. If you're attaching a Route exclusively to an HTTP listener, why would you need to redirect to 80 + HTTP?
Thanks for your reply @robscott, our case is that we have a public website with https://example.com, but we also have some API endpoints with http (http://example.com/api) that was feed to a legacy system, we cannot change the code for the legacy system.
I used Nginx Ingress Controller with the below before (with annotation to bypass some path from https), now I migrate to Gateway but it seems I cannot find the documentation about this.
What would you like to be added:
Documentation or example about confiuring single hostname with BOTH https and http path.
e.g. https://www.example.com/, http://www.example.com/foo
Why this is needed:
How to achieve single hostname with BOTH https and http path, e.g.:
"/" with https tcp443
"/plaintext" with http tcp80
Something like:
The text was updated successfully, but these errors were encountered: