fix: Incorrect parsing of Binary Content Mode cloud events #43
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.
Signed-off-by: Dimitar Milov dmilov@vmware.com
Description
Fixes issue #42. When Content-Type prefix other than
application/cloudeventsis used the event is considered to be binary mode. For the binary mode of HTTP there are headers that are required by the protocol. There was no handling of required headers which leads to the wrong behavior described in issue #42 .Added handling of required fields for binary content mode.
Closes: #(issue-number)
Type of change
Please mark options that are relevant:
not work as expected)
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide
instructions so we can reproduce. If applicable, please also list any relevant
details for your test configuration.
Test Configuration:
Checklist:
guidelines
of this project