-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Routing based on Request Header #360
Copy link
Copy link
Labels
RoutingOcelot feature: RoutingOcelot feature: RoutingSpring'24Spring 2024 releaseSpring 2024 releasefeatureA new featureA new featuremergedIssue has been merged to dev and is waiting for the next releaseIssue has been merged to dev and is waiting for the next release
Milestone
Metadata
Metadata
Assignees
Labels
RoutingOcelot feature: RoutingOcelot feature: RoutingSpring'24Spring 2024 releaseSpring 2024 releasefeatureA new featureA new featuremergedIssue has been merged to dev and is waiting for the next releaseIssue has been merged to dev and is waiting for the next release
Type
Fields
Give feedbackNo fields configured for issues without a type.
Hi,
I'm interested if Ocelot currently supports downstream routing to multiple endpoints based on a Request Header?
A use case for this is something like:
eg.
AU redirects to -> api.internal-au/products
UK redirects to -> api.internal-uk/products
cheers