dapr / dapr/dotnet-sdk

Follow-up: dotnet subscriber unable to receive published message from controller post method

Open
#665 1 comment 0 reactions 0 assignees View on GitHub
documentation
Dominant language
C#
Stars
1.2k
Forks
378
Avg merge
1d 22h
Merged PRs (30d)
5

Description

Following up on isssue #487, I can confirm that app.UseHttpsRedirection() is the culprit when using TopicAttribute or the YAML declarative subscription, which gives the following error:
```
time="2021-04-27T16:08:14.8816947-04:00" level=error msg="app returned http status code 500 from subscription endpoint" app_id=myapi instance=DESKTOP scope=dapr.runtime type=log ver=1.1.2
time="2021-04-27T16:08:14.882223-04:00" level=debug msg="app responded with subscriptions []" app_id=myapi instance=DESKTOP scope=dapr.runtime type=log ver=1.1.2
```
Commenting that line and using the HTTP application port fixes the issue (using the HTTPS application port never works).

#### Environment:
Windows 10
Dapr 1.1.2 self-hosted (w/ Docker, running the app using the Dapr CLI and docker-compose)
ASP.NET core 3.1 w/ Dapr.AspNetCore 1.1.0
Pub/Sub component: Azure Service Bus Topics

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.