Skip to content

Routing based on Request Header #360

@BrettJG

Description

@BrettJG

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:

  • Octolot receives a request for /products
  • The request has a header something like Region: AU / Region: UK
  • Based on the Region header field the request is routed to a matching downstream endpoint

eg.
AU redirects to -> api.internal-au/products
UK redirects to -> api.internal-uk/products

cheers

Metadata

Metadata

Assignees

Labels

RoutingOcelot feature: RoutingSpring'24Spring 2024 releasefeatureA new featuremergedIssue has been merged to dev and is waiting for the next release

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions