trivial: Fix X-Splunk-Request-Channel header logic in batch requests#77
Open
vladosentinelus wants to merge 1 commit intonatesmalley:mainfrom
Open
trivial: Fix X-Splunk-Request-Channel header logic in batch requests#77vladosentinelus wants to merge 1 commit intonatesmalley:mainfrom
vladosentinelus wants to merge 1 commit intonatesmalley:mainfrom
Conversation
- Only add X-Splunk-Request-Channel header for raw endpoint requests (/raw) - Remove header from JSON endpoint requests (/event) to prevent HEC rejection - Add missing uuid import to fix undefined name error - Maintain consistency with send_one() function behavior Fixes critical logic error where batch JSON requests were incorrectly receiving the raw endpoint header.
nate-smalls-s1
approved these changes
Mar 16, 2026
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
2 participants
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.
Fixes critical logic error where batch JSON requests were incorrectly receiving the raw endpoint header.