Skip to content

feat: display HTTP request headers in expandable section#268

Open
kapekost wants to merge 1 commit intoprobot:masterfrom
kapekost:feat/display-request-headers
Open

feat: display HTTP request headers in expandable section#268
kapekost wants to merge 1 commit intoprobot:masterfrom
kapekost:feat/display-request-headers

Conversation

@kapekost
Copy link
Copy Markdown

@kapekost kapekost commented Apr 1, 2026

Closes #270

Summary

When expanding a webhook delivery, a collapsible Headers section now appears above the payload. This surfaces HTTP metadata (content-type, signatures, custom webhook identifiers, etc.) that are currently stored in the event data but never displayed.

Before

  • Only x-github-event shown as event title; other headers hidden
  • Only the body payload is visible when expanded

After

  • Collapsible Headers tab shows all HTTP headers as a key-value table
  • GitHub webhook behavior is unchanged

Changes

  • src/components/ListItem.tsx: extract headers from event data, render in collapsible section

Motivation

smee.io is used beyond GitHub — any webhook producer can use it for debugging. HTTP headers often carry critical metadata (webhook type, signatures, trace IDs) that users currently cannot see without inspecting browser dev tools or running the CLI client. See #270 for details.

When expanding a webhook delivery, a collapsible "Headers" section now
appears above the payload. This surfaces metadata like content-type,
signatures, and custom webhook identifiers that were previously hidden.

For non-GitHub webhooks, the event title falls back to common header
patterns (x-*-event, x-*-webhook-*) so deliveries are identifiable
without expanding.

Made-with: Cursor
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.

Display HTTP request headers in the web UI

1 participant