-[Fixed an issue in Bulk Subscribe when App replied back with few specific kind of replies](#fixed-an-issue-in-bulk-subscribe-when-app-replied-back-with-few-specific-kind-of-replies)
-[Fixed Dapr accepting components with impossible names in standalone mode](#fixed-dapr-accepting-components-with-impossible-names-in-standalone-mode)
-[MongoDB Actor State Store: Fixed an issue with storing Actor Reminders](#mongodb-actor-state-store--fixed-an-issue-with-storing-actor-reminders)
-[Fixed a Goroutine leak in Actor reminders and timers.](#fixed-a-goroutine-leak-in-actor-reminders-and-timers)
-[Fixed an issue with Service Invocation on Kubernetes clusters with the permission enforcement admission controller enabled.](#fixed-an-issue-with-service-invocation-on-kubernetes-clusters-with-the-permission-enforcement-admission-controller-enabled)
-[Fixed issue with Azure Service Bus binding rejecting messages](#fixed-issue-with-azure-service-bus-binding-rejecting-messages)
## Fixed an issue in Bulk Subscribe when App replied back with few specific kind of replies
...
...
@@ -157,3 +158,25 @@ Services.
### Solution
We updated the Kubernetes RBAC permissions used by the Dapr Operator.
## Fixed issue with Azure Service Bus binding rejecting messages
### Problem
The following error message is logged by Daprd when using the Azure Service Bus binding, and the message will not be sent to the application.
"App handler returned an error for message xxx on queue shipments: error invoking app: Post "http://127.0.0.1:80/xxx": net/http: invalid header field name"
### Impact
Since v1.10.4, applications would not receive messages from Azure Service Bus bindings.
### Root cause
Azure Service Bus supports storing Application Proprieties which are not URL
safe.
### Solution
Daprd encodes metadata headers before sending messages to applications, so that
