Test: Validate method invocation with extraneous headers #1355
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.
Description
Added a unit test that verifies that if the developer creates an
HttpMessageRequest
viaCreateInvokeMethodRequest
on the DaprClient then appends additional headers to it, that these headers will be present on the intercepted HTTP request sent to the test client and not stripped away.Also, fixed a spelling typo in a related class.
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
This will not close #1352 but it just augments our existing unit test suite to close a gap.
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list: