I am facing following issue with the on-premises data gateway:
The on-prem API server is a Jetty, that responds with HTTP 1.1 Transfer-Encoding: chunked, if the request is valid.
If not, it responds with no Transfer-Encoding header but with Content-Length.
When I try to get the result with the HTTP with Azure AD connector making an invalid request, I get the data (with the error message) - the data gateway works fine then.
On the other hand, if the request is valid and the API response is chunked, the actions body will only show the header JSON including Content-Length: 0, but no data.
Unfortunately the admin of this API server does not find a way to make Jetty respond unchunked only.
Is this behavior really caused by the on-premises data gateway (and/or the action) not supporting chunked data?
