Skip to content

refactor(auth)!: standardize Fanout headers - #182

Merged
vishr merged 1 commit into
mainfrom
fix/standard-headers-v2
Aug 23, 2026
Merged

refactor(auth)!: standardize Fanout headers#182
vishr merged 1 commit into
mainfrom
fix/standard-headers-v2

Conversation

@vishr

@vishr vishr commented Aug 23, 2026

Copy link
Copy Markdown
Member

Summary

  • require Authorization: Bearer <token> for both OTLP/gRPC and OTLP/HTTP
  • rename X-Fanout-Request to Fanout-Request
  • rename X-Fanout-Confirm-Delete to Fanout-Confirm-Delete
  • update setup/settings metadata, benchmark traffic, README, operator docs, UI source, and embedded assets
  • explicitly test that the retired ingest header is rejected on both transports

Breaking changes

There is no legacy fallback. Collectors using x-fanout-ingest-token must move the same token to Authorization: Bearer <token>. Browser/API consumers must use the renamed Fanout headers.

OTLP/HTTP remains on the standard /v1/traces, /v1/metrics, and /v1/logs paths. No custom Fanout contract-version header is introduced.

Validation

  • just check
  • go test -race -gcflags=all=-d=checkptr=0 -coverprofile=/private/tmp/fanout-standard-headers.coverage ./... — 914 tests across 24 packages
  • focused Go tests — 384 tests across changed packages
  • UI tests — 27 tests
  • full binary and embedded-asset rebuild
  • gitleaks on the complete diff — no findings

Require Authorization: Bearer for OTLP/gRPC and OTLP/HTTP. Rename the browser mutation and delete confirmation headers.

BREAKING CHANGE: x-fanout-ingest-token, X-Fanout-Request, and X-Fanout-Confirm-Delete are no longer accepted.
@vishr
vishr merged commit 1e5e8c5 into main Aug 23, 2026
8 checks passed
@vishr
vishr deleted the fix/standard-headers-v2 branch August 23, 2026 04:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant