feat: display HTTP request headers in expandable section#268
Open
kapekost wants to merge 1 commit intoprobot:masterfrom
Open
feat: display HTTP request headers in expandable section#268kapekost wants to merge 1 commit intoprobot:masterfrom
kapekost wants to merge 1 commit intoprobot:masterfrom
Conversation
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
b6965c5 to
c8fd13d
Compare
This was referenced Apr 1, 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
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.
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
x-github-eventshown as event title; other headers hiddenbodypayload is visible when expandedAfter
Changes
src/components/ListItem.tsx: extract headers from event data, render in collapsible sectionMotivation
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.