-[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 a Goroutine leak in Actor reminders and timers.](#fixed-a-goroutine-leak-in-actor-reminders-and-timers)
-[MongoDB Actor State Store: Fixed an issue with storing Actor Reminders](#mongodb-actor-state-store--fixed-an-issue-with-storing-actor-reminders)
-[Fixed Dapr being unable to obtain the authentication token when using Managed Identity inside Azure App Service](#fixed-dapr-being-unable-to-obtain-the-authentication-token-when-using-managed-identity-inside-azure-app-service)
-[Fixed a problem where keys could not be overwritten once set in Microsoft SQL Server (and Azure SQL)](#fixed-a-problem-where-keys-could-not-be-overwritten-once-set-in-microsoft-sql-server--and-azure-sql-)
-[Fixed issue with Azure Service Bus binding rejecting messages](#fixed-issue-with-azure-service-bus-binding-rejecting-messages)
## Fixed an issue with Service Invocation on Kubernetes clusters with the permission enforcement admission controller enabled.
...
...
@@ -133,3 +134,25 @@ The runtime code for creating an application channel for non-localhost apps requ
### Solution
The application port validation was removed.
## 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 xxx: 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
