docs: Update reverse proxy guidance for Cloudflare and risky domain patterns#15413
Merged
rafaeelaudibert merged 3 commits intomasterfrom Mar 2, 2026
Merged
Conversation
…ph domain guidance - Add "ph" to the list of risky subdomain patterns that ad blockers target - Clarify that the proxy won't achieve its intended effect if ad blockers block the domain - Replace simple blockquote note with a prominent CalloutBox warning about disabling DNS provider proxy features (e.g., Cloudflare's orange cloud) Reflects changes from PostHog/posthog#49431
…49431 PR #49431 added `\bph\.` to the RISKY_DOMAIN_PATTERNS regex in proxyLogic.ts, meaning ad blockers now flag `ph` subdomains. Updated both Cloudflare Workers (Option 1) and DNS/Page Rules (Option 2) guidance to list `ph` as a term to avoid and suggest `t` instead.
…ngest PR #49431 added `\bph\.` to the RISKY_DOMAIN_PATTERNS regex, meaning subdomains starting with "ph" are now flagged by ad blockers. Updated: - Checklist: moved `/ph` to the "avoid" list, recommend `/e` or `/ingest` - CORS examples: replaced `/ph` with `/ingest` in both US and EU snippets - Fixed stray `**` formatting in checklist item
Contributor
Deploy preview
|
Contributor
|
Vale prose linter → found 0 errors, 17 warnings, 0 suggestions in your markdown Full report → Copy the linter results into an LLM to batch-fix issues. Linter being weird? Update the rules!
|
| Line | Severity | Message | Rule |
|---|---|---|---|
| 13:58 | warning | Use 'Cloudflare' instead of 'cloudflare'. | Vale.Terms |
| 25:38 | warning | 'proxying' is a possible misspelling. | PostHogBase.Spelling |
| 212:4 | warning | 'Option 2: DNS and Page Rules' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 226:21 | warning | 'Proxied' is a possible misspelling. | PostHogBase.Spelling |
| 309:124 | warning | 'IPs' is a possible misspelling. | PostHogBase.Spelling |
| 315:5 | warning | 'CORS errors in browser console' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 363:5 | warning | 'Unexpected token 'export' error in Worker' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 386:5 | warning | 'Page Rules not taking effect' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 392:55 | warning | 'proxied' is a possible misspelling. | PostHogBase.Spelling |
contents/docs/advanced/proxy/proxy-reference.mdx — 0 errors, 8 warnings, 0 suggestions
| Line | Severity | Message | Rule |
|---|---|---|---|
| 25:48 | warning | 'IPs' is a possible misspelling. | PostHogBase.Spelling |
| 58:58 | warning | 'proxying' is a possible misspelling. | PostHogBase.Spelling |
| 62:5 | warning | '405 Method Not Allowed' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 66:5 | warning | '502 Bad Gateway' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 76:5 | warning | 'CORS errors' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 106:36 | warning | 'IPs' is a possible misspelling. | PostHogBase.Spelling |
| 111:15 | warning | Use 'NGINX' instead of 'nginx'. | Vale.Terms |
| 123:45 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
rafaeelaudibert
approved these changes
Mar 2, 2026
rafaeelaudibert
approved these changes
Mar 2, 2026
Member
Merge activity
|
rafaeelaudibert
deleted the
docs-writer-ai-update-2026-03-02T17-30-49-952Z-h84ul8
branch
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.
Summary
Updates reverse proxy documentation to reflect changes from PostHog/posthog#49431, which added Cloudflare proxy warnings and improved domain guidance.
Changes
1. Added "ph" to risky domain patterns
The
RISKY_DOMAIN_PATTERNSregex in the app now includes\bph\.as a pattern that ad blockers flag. Updated docs to:phto the list of terms to avoid in subdomain namesphfrom safe pattern recommendations (replaced withtoringest)Files updated:
contents/docs/advanced/proxy/_snippets/managed-reverse-proxy.mdxcontents/docs/advanced/proxy/cloudflare.mdxcontents/docs/advanced/proxy/proxy-reference.mdx2. Improved Cloudflare DNS proxy warning
Added a prominent warning about disabling DNS provider proxy features (like Cloudflare's "orange cloud") when configuring CNAME records for PostHog's managed reverse proxy. Enabling the proxy at the DNS provider may interfere with PostHog's managed reverse proxy functionality and SSL certificate provisioning.
File updated:
contents/docs/advanced/proxy/_snippets/managed-reverse-proxy.mdx- Upgraded note toCalloutBoxwith type="caution"This PR was created by the Inkeep Content Writer agent, which is maintained by the Docs and Wizard team. Please reach out on Slack for help if needed.