This repository was archived by the owner on Jun 15, 2026. It is now read-only.
Feature/display request headers#34
Open
edward232232 wants to merge 9 commits into
Open
Conversation
added 9 commits
July 25, 2025 13:53
- Enhanced Event Grid Viewer to show HTTP request headers alongside event data - Added tabbed interface to switch between event data and headers - Created header count badge for quick reference - Filtered headers to show only relevant Event Grid and HTTP headers - Added test script to verify functionality - Maintained backward compatibility with existing functionality Features: - View aeg-* headers (event-type, data-version, metadata-version, etc.) - Display common HTTP headers (content-type, user-agent, etc.) - Clean JSON formatting for headers display - Improved UI with Bootstrap tabs
- Removed complex tabs and extra table column - Headers now display below event data in simple format - Maintains original table structure and UI layout - Only shows headers when they exist - Minimal code changes from original repository - Removed unused EventWithHeaders model Changes: - UpdatesController.cs: Added header capture and forwarding - Index.cshtml: Simple headers display below event data - Only 2 files modified from original repo
- Add GetRequestHeaders() method to capture all HTTP headers - Display headers in collapsible sections below event data - Minimal changes to core functionality for debugging
- Add GetRequestHeaders() method to capture HTTP headers - Display headers in UI below event data for debugging - Only essential changes for the core feature
Clean implementation with minimal diff: - Only core files modified for headers display feature - 37 additions, 7 deletions across 2 files
Author
|
@microsoft-github-policy-service agree |
Author
|
@dbarkol any chance you could look into this PR? |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Purpose
Adds HTTP request headers display to the Event Grid viewer for debugging and troubleshooting purposes
Does this introduce a breaking change?
Pull Request Type
What kind of change does this Pull Request introduce?
How to Test
-H "Content-Type: application/json"
-H "Authorization: Bearer test-token"
-H "Custom-Header: test-value"
-d '[{"id":"test-id","eventType":"test.event","subject":"test","eventTime":"2025-01-01T00:00:00Z","data":{"test":"data"}}]'
What to Check
Verify that the following are valid
Headers are displayed below event data in the UI
Headers section only appears when headers are present
All existing Event Grid viewer functionality works unchanged
Headers display for validation, grid events, and cloud events
Headers are formatted as readable JSON
Other Information