docs: TLS-fingerprint walls, where the impersonated tier helps - #533
Merged
Merged
Conversation
Turns the site-coverage research behind us#527 into a user-facing page: the three gate shapes (TLS-only, JavaScript, combined vendor) with verified examples and dates, the IP-rate anti-pattern (identical errors on two TLS stacks mean pacing, not impersonation), a three-step diagnosis that works from whatever egress crw runs on, and the extension recipe for covering another marketplace's interstitial (verify the sentence against a live wall before adding it, with positive and negative fixtures). Linked from the js-rendering pin table. gate-exempt: documentation-only change (new page, one pointer, sidebar registration); docs-guards and the internal link check pass locally. Gates: /simplify, code-review
Adapt the research notes to the documentation register the rest of the site uses: page-intro block with Covers/Verified-against, symptom-first structure, imperative voice instead of probe narration, a blockquoted "not a fingerprint problem" note mirroring the troubleshooting page's "not a block" pattern, and managed-cloud plus self-hosted cURL examples for the diagnosis steps. Same facts, same scope. Gates: /simplify, code-review
Owner
|
thank you for that @paoloantinori 🫶 |
us
self-requested a review
September 11, 2026 11:44
us
previously approved these changes
Sep 11, 2026
us
force-pushed
the
docs/tls-walls-site-coverage
branch
from
September 11, 2026 11:48
a22669c to
6549fad
Compare
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.
2 participants
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.
Follow-up to #527, documentation only.
While validating the impersonated-http tier I ran an A/B probe (plain HTTP vs the impersonated pin, same egress) across the site classes people actually ask about, and the result is worth shipping as a page rather than staying in a PR thread: the wall landscape splits into three gate shapes, and only one of them is what the tier fixes.
The new page (
docs/tls-fingerprint-walls.md, linked from the JS-rendering pin table) covers:#[ignore]live tests as the sentinel.Local checks:
scripts/docs-guards.shandscripts/check-doc-links.shpass (the page is registered indocs/site.config.js; 50 known slugs, no broken links).