Feat/server timing reporting - #14
Merged
Merged
Conversation
What: - Parse standard Server-Timing metrics, descriptions, and signals. - Aggregate coverage, percentiles, and the ten worst pages. - Expose timing data through page and result APIs. Why: - Make Rails and custom backend instrumentation actionable in crawl reports. - Preserve malformed-entry visibility without hiding valid metrics. Where: - Server-Timing parser, summary, and reporter components. - HTTP and browser page snapshots, documentation, and focused tests.
What: - add a callable profile_token configuration that emits X-Profile-Token - propagate the token through sitemap, HTTP, and browser document requests - retain same-origin redirects while stripping cross-origin requests Why: - allow protected Server-Timing endpoints to be crawled and reported - prevent diagnostic credentials from leaking to third-party origins Where: - request header policy, crawl transports, configuration, documentation, and transport tests
What: - Fetch the implicit sitemap from the configured HTTP base URL. - Resolve profile tokens from CRAWLSCOPE_PROFILE_TOKEN by default. - Update the Rails initializer template and migration guidance. Why: - Keep validation tied to live application and database state. - Support secure token configuration in Rails, CLI, Rake, and plain Ruby usage. Where: - Runtime configuration and default sitemap resolution. - Rails install generator, documentation, and focused regression tests.
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
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.
How to test
Release notes
Does this change need an explicit changelog or release-note callout beyond the PR title?
Checklist
About the maintainers
Built by Ethos Link, the team behind Reviato.
Capture. Interpret. Act.
Turn guest feedback into clear next steps for your team. Collect private appraisals, spot patterns across reviews, and act before small issues turn into public ones.