Enforce lower-kebab-case for resource http headers#363
Merged
Conversation
BenoitZugmeyer
approved these changes
Mar 4, 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.
Summary
Add a propertyNames constraint to both request.headers and response.headers in the resource schema, ensuring all header keys follow lowercase kebab-case format (e.g. content-type, x-request-id).
Motivation
HTTP header names collected in RUM resource events should be normalized to lowercase kebab-case for consistency. This schema-level validation prevents ingestion of headers with mixed casing (e.g. Content-Type) or non-standard separators (e.g. x_request_id), ensuring uniform keys across all resource events.
Changes
schemas/rum/resource-schema.json: Added propertyNames.pattern set to ^[a-z][a-z0-9](-[a-z0-9]+)$ on the headers object in both resource.request and resource.response.