Fix: Send content-type header even when payload does not exist#20
Draft
shasts wants to merge 1 commit intoelastic:masterfrom
Draft
Fix: Send content-type header even when payload does not exist#20shasts wants to merge 1 commit intoelastic:masterfrom
shasts wants to merge 1 commit intoelastic:masterfrom
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 of the PR
We have test failures where API validates for
content-typeheader, but if the payload is empty, the swagger client does not seem to send it. https://github.com/elastic/cloud/issues/100076This PR fixes the
ApiInvokerto send thecontent-typeforPOST,PUT, andPATCHeven when the payload is empty. Looks like thescalaclient is not the only one doing it. swagger-api#7787