fix(docs): correct cross-language inconsistencies and add missing features - #43
fix(docs): correct cross-language inconsistencies and add missing features#43forgetso wants to merge 3 commits into
Conversation
Replaces the one-paragraph mention of the disposable-domain blocklist with full coverage of the five-stage check chain (direct lookup, SSRF-safe validation, HTTPS redirect probe, CNAME chase, MX fallback), provider-side config (`spamEmailDomainsUrls`, scheduler cron) and the standalone `/v1/prosopo/provider/client/spam/email` endpoint with request/response examples. Also updates the evaluation-order list to reflect that the domain-list stage runs last (after the synchronous pattern rules) since it is the most expensive. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Cuts implementation detail that doesn't belong on customer-facing docs: the SSRF safety check, source-code paths, the provider-side feed URLs and cron config, and the per-step DNS-chase explanation. What's left: what the toggle does, what gets caught (including the redirect/CNAME/MX chase, named but not over-explained), the rejection status code, and the standalone endpoint contract. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…tures Cross-language fixes (en + de/es/fr/it/pt-br): - Fix broken React integration links in welcome and client-side-rendering (pointed at /angular-integration/ instead of /react-integration/) - Fix invisible-captcha server-side example using reCAPTCHA-style fields (response/remoteip/result.success) instead of Prosopo's (token/ip/verified) - Fix server-side-verification SDK example: ProsopoServer requires a pair argument; isVerified returns a VerificationResponse object, not a boolean - Fix tier naming "Pro and Enterprise" -> "Professional and Enterprise" to match the Tier enum in the portal English-only: - Add ASN as a documented access-control rule field (already supported by the rule editor and policy schema, just undocumented) - Reword traffic-filter "Providing the IP Address" to lead with what actually happens (filters always run against the session-initiation IP; passing ip overrides with a fresh lookup) instead of implying the IP field is required Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
✅ Deploy Preview for peaceful-pothos-9e62ce ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
No updates since Nothing is lost — Converting to draft disables auto-merge, so PRs with auto-merge enabled are excluded from this entirely. |
|
No updates since Nothing is lost — Converting to draft disables auto-merge, so PRs with auto-merge enabled are excluded from this entirely. |
Summary
Cross-language fixes (en + de/es/fr/it/pt-br):
welcome/andbasics/client-side-rendering.mdxpointed at/angular-integration/instead of/react-integration/(24 instances across 12 files).response,remoteip,result.success) instead of Prosopo's (token,ip,verified). MatchesApiParamsandVerificationResponseincaptcha/packages/types.new ProsopoServer(config)would crash at runtime becauseverifyProviderrequirespair.sign(...). Now passespairviagetPair(). Alsoif (await isVerified(...))treated the returned object as a boolean — fixed to unpackresult.verified. JS fetch example missingawaitonresponse.json().Tierenum in the portal (packages/portal/src/components/AccountComponents/UpgradeModal.tsx).English-only:
RuleEditorFields.tsand the policy schema (captcha/packages/user-access-policy/src/rule.ts), just undocumented.ipoverrides with a fresh lookup). Previous wording implied theipfield was required.Test plan
🤖 Generated with Claude Code