Fragile routing and no debug help

[davidmw]

When the proxies.json becomes longer than just a few routes it is quite difficult to identify and fix routing problems.

Seems like any error in any route will keep all routes from functioning. For one example, I had "backendUri": "https:/www....." missing a backslash in the URL. All routes stopped working until fixing this and the errored route was at the bottom of the file.

It would be great to have some debugging support but this isn't working:

By adding the flag "debug":true to any proxy in your proxies.json, you'll enable debug logging. Logs are stored in D:\home\LogFiles\Application\Proxies\DetailedTrace and accessible through the advanced tools (kudu). Any HTTP responses will also contain a Proxy-Trace-Location header with a URL to access the log file.

As far as I've been able to determine, the extension isn't generating any logs with visibility in Kudu and all errors / failures are silent so it is pretty tedious to determine if and which route is broken.

[davidmw]

That quote above is from Microsoft documentation.