Package not compatible with .NET Client package

[Ackhuman]

There is an issue with the default function name being "HttpTrigger1". Every other JsReport instance sits the API endpoint at "/api/report", which is how the .NET Client package is configured to work. You simply provide the base URL, which it sets as the BaseUrl property in the internal HttpClient. However, when it sends the request, it always uses "api/report" as the request URL. With the out of the box configuration of the Azure function, the API endpoint will be "/api/HttpTrigger1", which means attempting to use the two together will result in a 404. The default function name should therefore be changed from "HttpTrigger1" to "report" to enable compatibility between the two.

[pofider]

Thank you.

But the current function code doesn't return the render response in the same shape as the standard jsreport server, so not sure how this helps. Are you actually able to read the response properly with the .net client after the change?

[Ackhuman]

Sorry for the late reply. Yes, I had no trouble reading the response using the .NET Client package with no additional changes. Before my change I had just been doing the exact same thing but using the different URL.