Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Response headers are not part of the response object #605

Closed
Rajesh91-ch opened this issue Jul 6, 2024 · 2 comments
Closed

Response headers are not part of the response object #605

Rajesh91-ch opened this issue Jul 6, 2024 · 2 comments
Labels

Comments

@Rajesh91-ch
Copy link

Rajesh91-ch commented Jul 6, 2024

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);

@dapr-bot
Copy link
Collaborator

dapr-bot commented Sep 4, 2024

This issue has been automatically marked as stale because it has not had activity in the last 60 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

@dapr-bot dapr-bot added the stale label Sep 4, 2024
@dapr-bot
Copy link
Collaborator

This issue has been automatically closed because it has not had activity in the last 67 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue, help wanted or triaged/resolved. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants