How to map internal endpoint in Ocelot API gateway?

[lujamaharjan]

When i use
await app.UseOcelot()
The endpoints in the same project where ocelot is configured do not work. I get 404. Is there any way to map internal routes.

[raman-m]

Hello, Sachin!

What endpoints are you referring to? How were they established? What is the actual type of the 404 error? Could you please extract the logs?

Did you mean the Ocelot controller endpoints or user type ones? Could you provide the complete C# code?

[raman-m]

I'm curious about the necessity for additional controllers in a product whose primary function is to forward API requests. If research is required, please conduct it independently.
Please find another public GitHub repository for some fun❗

[lujamaharjan]

so, write now, it does not support minimal API and ocelot in same asp.net project?

[raman-m]

#1949 (comment)

You should Map controller routes after UseOcelot, not before!

var app = builder.Build();
await app.UseOcelot(); // before your custom MapGet
app.MapGet("/test", () => "Hello World!");
app.Run();

Hope it helps!

[lujamaharjan]

hi, the endpoint after UseOcelot() also not worked. For /test also, ocelot is trying to find downstream url.

[raman-m]

All URL paths in Ocelot, including /test, serve as upstream paths used to forward requests to downstream service paths, with middlewares transforming the requests along the way. Ocelot identifies a route with the /test upstream path and prepares to transform the request before finally forwarding it to the downstream service.
If a route with /test upstream was not found in ocelot.json configuration, then Ocelot correctly returns 404.

[raman-m]

How to map internal endpoint in Ocelot API gateway?

Ocelot is not designed to host endpoints because it's a routing software! It doesn't act as an API endpoint host; instead, Ocelot functions as a traffic router based on routes and URL paths ❕ At last, Ocelot functions as a reverse proxy!

The endpoints in the same project where ocelot is configured do not work. I get 404. Is there any way to map internal routes.

404 is correct behavior. In Getting Started chapter we don't recommend attaching additional endpoints via app.Map* methods. The Ocelot pipeline is not compatible with classic API endpoints for hosting.

Is there any way to map internal routes.

app.MapGet("/test", () => "Hello World!");

Your small minimal API endpoint suggests that you intend to use it as a downstream service. Deploy and implement this service independently from Ocelot, and ensure your client connects directly to this endpoint without relying on Ocelot routing ❗ It's entirely up to you whether to route the traffic using Ocelot as a route or not.

If the recipes mentioned in #1949 don't work, there might be an undocumented configuration, the MapWhenOcelotPipeline property, introduced by PR #416 (refer to commit 5c940ac). It wasn’t originally intended as a feature, so it wasn’t thoroughly tested, but it seems like it could serve as a feature for extending the Ocelot pipeline with additional endpoints.