Guillaume Gnaegi

> > @ggnaegi commented [on Mar 9](https://github.com/ThreeMammals/Ocelot/pull/1914#issuecomment-1986859626) > > The problem is that your design of the delegate was reused in the new delegate class by Raynald. > So, seems...

@raman-m first we should check if the issue is solved then update the docs ;-)

> Absolutely not. "Ocelot" configurations can be very long, and mixing them up in appsettings.json seems counter-productive. Even if you could make one or more partial appsettings.ocelot.json files, I don't...

@ArwynFr @raman-m To be honest, I don't know why we are creating a new service provider. I'm using the ```IOcelotBuilder AddOcelot(this IServiceCollection services, IConfiguration configuration)``` extension method myself, avoiding creating...

@ArwynFr Ok, it makes sense from architectural standpoint. From my side, I don't like that kind of black box approaches. But, yes you are right, it's the current approach with...

@ArwynFr @raman-m It's probably the whole IOcelotBuilder logic that should be rewritten. It's a bit like what we have seen with the IOcelotLogger or the Http Client Pool. Some layers...

@raman-m I would say so, we have reworked that part lately. Maybe it was a bug in version 13, maybe the user had to reference polly in his project?

@raman-m Ok, maybe @ks1990cn would be willing to perform the validation for us?

@MatheusXavier you should fork the repo, then create your own branch in the forked repo. When you are ready, you can from there create a PR. 

```json { "DownstreamPathTemplate": "/OPUIAPI/signalr", "DownstreamScheme": "ws", "DownstreamHostAndPorts": [ { "Host": "bthsa1163.infineon.com", "Port": 8001 }, { "Host": "bthtsa1030.infineon.com", "Port": 8000 } ], "UpstreamPathTemplate": "/gateway/opui/signalr", "UpstreamHttpMethod": [ "Get", "Put", "Post", "Delete", "Options"...