Cherry-pick #20232 to 7.x: [Filebeat Input][HTTP_endpoint] Add possibility to override content-type header#20236
Merged
marc-gr merged 1 commit intoelastic:7.xfrom Jul 28, 2020
Merged
Conversation
Contributor
|
Pinging @elastic/siem (Team:SIEM) |
Contributor
leehinman
approved these changes
Jul 27, 2020
…ertain webhooks that is not able to set content-headers at all. Still defaults to application/json (elastic#20232) (cherry picked from commit 98a423d)
5f2904d to
34c5785
Compare
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
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.
Cherry-pick of PR #20232 to 7.x branch. Original message:
What does this PR do?
Webhooks like Zoom does not add any content-type headers on incoming requests, the content type now defaults to application/json but is possible to set to another value or null.
This is a preliminary change needed before adding some more validation steps, which will be created in separate PR's
Why is it important?
Adds support for webhooks which does not set content-type headers.
Checklist
- [ ] I have added an entry inCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.