Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

in_opentelemetry: handle missing or invalid content-type headers in metrics and traces handlers #8986

Merged
merged 2 commits into from
Jun 24, 2024

Conversation

portswigger-tim
Copy link
Contributor

Fixes #8983

Enter [N/A] in the box, if an item is not applicable to your change.

Testing
Before we can approve your change; please submit the following in a comment:

  • [N/A] Example configuration file for the change
  • [N/A] Debug log output from testing the change
  • [N/A] Attached Valgrind output that shows no leaks or memory corruption was found

If this is a change to packaging of containers or native binaries then please confirm it works for all targets.

  • [N/A] Run local packaging test showing all targets (including any new ones) build.
  • [N/A] Set ok-package-test label to test for all targets (requires maintainer to do).

Documentation

  • [N/A] Documentation required for this feature

Backporting

  • Backport to latest stable release.

Fluent Bit is licensed under Apache 2.0, by submitting this pull request I understand that this code will be released under the terms of that license.

@portswigger-tim portswigger-tim changed the title fix: add null content-type header check to traces and metrics endpoints in_opentelemetry: handle missing or invalid content-type headers in metrics and traces handlers Jun 20, 2024
@edsiper edsiper added this to the Fluent Bit v3.1.0 milestone Jun 20, 2024
@edsiper edsiper merged commit 9ed8cf8 into fluent:master Jun 24, 2024
57 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

SIGSEGV when none otlp traffic received on traces or metrics endpoint
2 participants