Guillaume Gnaegi

@raman-m The error handling is hiding the 413 exception payload too large. I've tested this with Kestrel, it's throwing a `BadHttpRequestException`. I will create a PR as soon as I...

@raman-m it's very old...

> @ggnaegi Oh, no! > We forgot to check this user scenario before the release 😏 Ouch...

@raman-m @camilocalderont @RaynaldM By design, if only one route, then when don't make any further checks and process the downstream request. It's a bit straight forward, but that's the way...

@nikhillkumar @raman-m you still have an option, it's adding your own logic here: https://github.com/ThreeMammals/Ocelot/blob/develop/src/Ocelot/Requester/MessageInvokerPool.cs#L85 You could even go a step further and use DI. ```c# RemoteCertificateValidationCallback = (sender, certificate, chain,...

@raman-m Yes, I just gave a solution to @nikhillkumar, but the feature should be implemented imo.

> @ggnaegi > > > the feature should be implemented imo. > > By whom? By Mr. Kumar? I think we should first convert this to a discussion and talk...

@raman-m it has been reopened.

> Gui, thanks for the new issue! > > > (Consul, Eureka...) > > What about ServiceFabric? > Can this upgrade be applied to ServiceFabric? @raman-m yes, but should I...

@raman-m We could keep it like that for now. I don't think polling has been foreseen for ServiceFabric. It's not that complicated to extract the provider though, but as you...