docs: improve https with cdn guide #821
Merged
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.
TASK-80256
Note
Low Risk
Documentation-only updates (text and images) with no product or code-path changes; risk is limited to potential user confusion if UI labels diverge from the current app.
Overview
Updates the CDN-based HTTPS engagement tracking doc to replace the old API-driven “set
secure: true” instructions with UI-based steps for enabling HTTPS via self-managed (CDN/reverse proxy), including new screenshots.Refines the managed HTTPS doc with updated UI wording/screenshot for enabling managed certificates and adds a new troubleshooting section showing how to
curl -va tracking URL to confirm the served Let’s Encrypt certificate details.Written by Cursor Bugbot for commit 9493a7a. This will update automatically on new commits. Configure here.