Filter out headers with empty values #5866
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Note - we probably don't want to filter out for everything because this behavior is only buggy for Node.js. Correct approach is through capabilities and either explicitly opting out of those or introducing a new headers property that is typed correctly. |
|
Why do we have to do this? |
|
@mathewc - because of the way we implemented headers in our protobuf schema (as a map<string, string>) and the "map" type doesn't accept empty values for runtimes like node. Causes buffer overrun and corrupts other parts of the message :( Azure/azure-functions-nodejs-worker#142 and Azure/azure-functions-language-worker-protobuf#21 |
|
@mhoeger this was originally opened against |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.