You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my setup, a Node.js app is deployed in an Azure container app with Dapr enabled. Another Node.js app consumes it using Dapr Service Invoke methods. When a request is made via Dapr Service Invoke, the response object contains only the 'Actual data' without any response headers or status code properties. However, when the same API is invoked using an HTTP call, the response object contains the 'Actual data' along with response headers and status code.
Is it a behavior of the Dapr service invoke call? Or Am i missing something?
Below is the signature of my api call: Dapr service invoke: const response = await daprClient.invoker.invoke('https://sampleurl.com/reports/${req.params.reportId}/status`, HttpMethod.GET);
The text was updated successfully, but these errors were encountered:
Hello,
In my setup, a Node.js app is deployed in an Azure container app with Dapr enabled. Another Node.js app consumes it using Dapr Service Invoke methods. When a request is made via Dapr Service Invoke, the response object contains only the 'Actual data' without any response headers or status code properties. However, when the same API is invoked using an HTTP call, the response object contains the 'Actual data' along with response headers and status code.
Is it a behavior of the Dapr service invoke call? Or Am i missing something?
Below is the signature of my api call:
Dapr service invoke: const response = await daprClient.invoker.invoke('https://sampleurl.com/reports/${req.params.reportId}/status`, HttpMethod.GET);
The text was updated successfully, but these errors were encountered: