docs/release_notes/v1.13.2.md
This update includes bug fixes:
Published messages to HTTP application server report a content-length error and are not processed.
PubSub messages from some PubSubs cannot be processed by the application.
The content-length reported by the PubSub broker message was copied to the message sent to the application's HTTP server. This content-length may not match the final message length sent to the application's HTTP server, resulting in the mesage being rejected.
Filter out the content-length header from the PubSub broker message before sending it to the application's HTTP server.
During a blocked shutdown, all in-flight PubSub messages are cancelled and cannot be processed by the application or the applications processes status discarded.
During shutdown, in-flight messages which are currently being processed by the application cannot be completed.
During shutdown, all publish calls to the application where being cancelled.
PubSub messages are now published to the application in an isolated routine, which is not cancelled during blocked shutdown.
When using Avro schema validation with the Kafka pub/sub component, consuming messages with a null value will fail and not be delivered to the app, and publishing messages with null values will fail.
Kafka messages with null values for both consumers and publishers are not delivered or published when using the Avro schema validation feature.
The Dapr component did not have correct handling of null values in a message.
Handling of null values was added when serializing and deserializing messages.