Error net/http: invalid header field value for \"__key\ in Dapr version 1.13.5 on Windows machine

[teachmeabhinav]

Expected Behavior

When you run application on windows it should subscribe and forward the message to application route in version 1.13.5 of Dapr on windows machine

Actual Behavior

When you run application on windows it is subscribing but not forwarding the message to application route in version 1.13.5 of Dapr however it was working perfectly fine in version 1.12.4 on windows machine.
Please refer to attached screen shot

It give the error "net/http: invalid header field value for "__key""
It don't see any issue in Linux

Machine configuration Windows 10

Steps to Reproduce the Problem

• Upgrade the Dapr form version 1.12.4 to 1.13.5 on your windows machine
• Run you application
• you will the error

Release Note

[rokrust]

I'm getting this issue on version 1.13.2 as well. In my case I have set up a kafka input binding.

[sandeepm1980]

I am having same issue. Kafka pubsub is not working on Windows platform. It's a blocker for us. It used to work in 1.12 verson and before. Please fix ASAP

[yaron2]

I am having same issue. Kafka pubsub is not working on Windows platform. It's a blocker for us. It used to work in 1.12 verson and before. Please fix ASAP

Hi, I'm a Dapr maintainer. Please ping me on Dapr Discord. My handle is yaron2

[chetnamittal]

I am having the same issue
It does not work in windows platform
This used to work in previous versions
Can you please help us by getting this fixed

[yaron2]

This issue is being worked on now and will be fixed for Dapr 1.14.2

[yaron2]

Hi all,

Dapr 1.14.2-rc.1 is out - please see if it fixes your issues and give feedback here

[teachmeabhinav]

@yaron2 We are able to get message after updating to 1.14.2-rc.1

[yaron2]

@yaron2 We are able to get message after updating to 1.14.2-rc.1

Great validation, thanks!

[passuied]

@yaron2 we'll be testing this version shortly too

[passuied]

Validated the fix on our end and we're also good with it! Thanks a lot for the quick turnaround

[yaron2]

Validated the fix on our end and we're also good with it! Thanks a lot for the quick turnaround

Thanks! We'll now go ahead and release the patches

[passuied]

@yaron2 actually, I think we may have an issue. The additional encoding is breaking some code as it's encoding = for instance which is a valid ascii character.
So it is making the change non-bw compatible which may break many consumers...

[yaron2]

Hi all, we now have Dapr 1.14.2 out with the fix - please notice its OPT-IN: https://docs.dapr.io/reference/components-reference/supported-pubsub/setup-apache-kafka/#receiving-message-headers-with-special-characters