Path Prefix about ocelot HOT 6 CLOSED

@danny-waite I had a look at that pathprefix and tbh didn't really get it :( I can be a bit stupid. Could you explain to me exactly what you want to do?

I'm thinking rather than defining all your incoming requests with the API gateway you want to have some kind of easy to define convention that just works for most / all of your incoming requests?

Ocelot wasn't designed with that in mind initially thought it would be a good feature.

If I was you I would go with traefik! Seems to be quite decent. Kong and Tyk look good too.

from ocelot.

@TomPallister

In my case I have 3 api and I only want redirect the traffic via Ocelot, I thinked in the following configuration:

{
      "UpstreamPathTemplate": "/api/api1/{urlPath}",
      "UpstreamHttpMethod": "Get",
      "DownstreamPathTemplate": "/api/{urlPath}",
      "DownstreamScheme": "http",
      "DownstreamHost": "localhost",
      "DownstreamPort": 5001,
      "QoSOptions": {
        "ExceptionsAllowedBeforeBreaking": 3,
        "DurationOfBreak": 10,
        "TimeoutValue": 10000
      }
    },
    {
      "UpstreamPathTemplate": "/api/api2/{urlPath}",
      "UpstreamHttpMethod": "Get",
      "DownstreamPathTemplate": "/api/{urlPath}",
      "DownstreamScheme": "http",
      "DownstreamHost": "localhost",
      "DownstreamPort": 5002,
      "QoSOptions": {
        "ExceptionsAllowedBeforeBreaking": 3,
        "DurationOfBreak": 10,
        "TimeoutValue": 10000
      }
    },
    {
      "UpstreamPathTemplate": "/api/api3/{urlPath}",
      "UpstreamHttpMethod": "Get",
      "DownstreamPathTemplate": "/api/{urlPath}",
      "DownstreamScheme": "http",
      "DownstreamHost": "localhost",
      "DownstreamPort": 5003,
      "QoSOptions": {
        "ExceptionsAllowedBeforeBreaking": 3,
        "DurationOfBreak": 10,
        "TimeoutValue": 10000
      }
    },

The requests to:

/api/api1 is redirected to port 5001
/api/api2 is redirected to port 5002
/api/api3 is redirected to port 5003

When I do a request to /api/api1/values works fine but with /api/api1/values/5 not works.
In the last case my api receive the request /api/values instead of /api/values/5.
Seems that the problem is with the parameters or slash character.

Maybe the problem is in the class UrlPathPlaceholderNameAndValueFinder.cs like you comment in post #74

It´s possible develop this? The idea it´s not to have to edit de configuration.json of our gateway every time we add new controllers to api1, api2 and api3. In this way, we have only edit the configuration.json when we need add a new api.

Thanks.

from ocelot.

Hi @TomPallister

I created a fork of your project and created a branch to add this functionality. The changes are only a couple of lines. I don´t know if you want add this to your project. In affirmative case, say me what I must to do, because it´s my first time on github.

Thanks.

from ocelot.

@juancash looks good, i left a comment on the PR if you could take a look. Thanks very much for your efforts!!

from ocelot.

@tom Acceptance test added to the PR #89.
Thanks to you for this great project.

from ocelot.

@juancash thank you once again, I really liked the way you made this change! Very simple 👍

from ocelot.