Can common config be written in "GlobalConfiguration"

Expected Behavior / New Feature

The documentation states: The Global configuration is a bit hacky and allows overrides of Route specific settings. It’s useful if you don’t want to manage lots of Route specific settings.

Based on this, my understanding is that if the following few configurations are common for all the entries in ReRoutes, then the following way of putting it together should work:

"GlobalConfiguration": {
    "DownstreamScheme": "https",
    "DangerousAcceptAnyServerCertificateValidator": true,
    "QoSOptions": {
        "TimeoutValue": 60000
    }
}

Actual Behavior / Motivation for New Feature

It is not working at my end. Looks like one of the possibilities:

1. My understanding is wrong: Then documentation should be made more explanatory.
2. My understanding is right: Ocelot may have some problem. Since this configuration otherwise (if I repeat these in each entry in ReRoutes) has been working for 20 services that my Ocelot instance is serving.

In either case, please help!

[gao-artur]

Looks like GlobalConfiguration section is limited for specific scenarios. Check this file to see what can be configured via GlobalConfiguration. But you can extend it with PostConfigure trick. Check my answer on SO for example.

[nedimg]

Any updates on this? This would be a very nice feature to have…