Yes this is my use case.
I can also confirm that the “Content-Type” header is being passed from the client, however I am experiencing some strange behaviour.
When I hard-code the authorization header I can hit my backend successfully, however it is not returning the correct data format. My backend should return JSON data (based on the url ending with “.json” and having the “Content-Type” header set to “application/json”) - which it does when I call it directly. However when I call it via DF, with exactly the same request, I get an HTML rendered page which is the expected response if I were to hit the backend service without the Content-Type header or without appending “.json” to the URL.
It would appear that the above problem has now resolved itself (bizarrely!) but I’m now facing an issue with passing url parameters across to my backend (i.e. f.clientId, f.contractorName, f.status, etc. as filter parameters for list endpoints).
This leads me to believe that DF is not passing on URL parameters with certain characters in the name.