Skip to content

docs: move cookie-domain guidance to troubleshooting faq#770

Merged
RiskeyL merged 1 commit into
mainfrom
docs/cookie-domain-faq-relocation
Apr 30, 2026
Merged

docs: move cookie-domain guidance to troubleshooting faq#770
RiskeyL merged 1 commit into
mainfrom
docs/cookie-domain-faq-relocation

Conversation

@RiskeyL
Copy link
Copy Markdown
Contributor

@RiskeyL RiskeyL commented Apr 30, 2026

Summary

  • Moves the cross-subdomain cookie-domain guidance from the Docker Compose quick-start callout to a new "Reverse Proxy Setup" entry in the FAQ. The original placement targets readers at the wrong moment: the issue surfaces at login-failure time after a reverse-proxy deployment, not at the .env-edit step during install. The FAQ entry is symptom-anchored ("Login Session Drops with Split Frontend and Backend Subdomains") so operators searching for the bug find it.
  • Mirrored across en, zh, and ja.
  • Cleans up pre-existing formatting issues in the same six files: heading title case, trailing whitespace, code-block spacing, missing bash language tags, and CJK-Latin spacing throughout the Japanese page.

COOKIE_DOMAIN and NEXT_PUBLIC_COOKIE_DOMAIN remain fully documented in the env vars reference, which the new FAQ entry links to.

Copilot AI review requested due to automatic review settings April 30, 2026 03:11
@mintlify
Copy link
Copy Markdown
Contributor

mintlify Bot commented Apr 30, 2026

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
dify-core-product 🟢 Ready View Preview Apr 30, 2026, 3:13 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@dosubot dosubot Bot added the size:L This PR changes 100-499 lines, ignoring generated files. label Apr 30, 2026
@dosubot dosubot Bot added the documentation Improvements or additions to documentation label Apr 30, 2026
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Moves cross-subdomain cookie-domain guidance to a symptom-driven FAQ entry so operators can find it when diagnosing reverse-proxy login/session issues, and aligns formatting across EN/JA/ZH quick-start docs.

Changes:

  • Adds a new “Reverse Proxy Setup” FAQ entry covering session drops when frontend/backend are on different subdomains, with COOKIE_DOMAIN + NEXT_PUBLIC_COOKIE_DOMAIN guidance.
  • Removes the same guidance from the Docker Compose quick-start callout to avoid surfacing it too early in the install flow.
  • Fixes minor formatting issues (heading capitalization, whitespace, code block language tags, and spacing) across the touched docs.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.

Show a summary per file
File Description
en/self-host/quick-start/faqs.mdx Adds reverse-proxy FAQ entry; normalizes heading title case.
en/self-host/quick-start/docker-compose.mdx Removes cookie guidance callout; adds bash language tag to restart snippet.
zh/self-host/quick-start/faqs.mdx Adds reverse-proxy FAQ entry in Chinese; removes stray whitespace line.
zh/self-host/quick-start/docker-compose.mdx Removes cookie guidance callout; fixes spacing around links; adds bash language tag.
ja/self-host/quick-start/faqs.mdx Adds reverse-proxy FAQ entry in Japanese; fixes CJK-Latin spacing.
ja/self-host/quick-start/docker-compose.mdx Removes cookie guidance callout; applies consistent spacing/formatting and adds bash language tag.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@RiskeyL RiskeyL merged commit 4ced86f into main Apr 30, 2026
6 of 7 checks passed
@RiskeyL RiskeyL deleted the docs/cookie-domain-faq-relocation branch April 30, 2026 03:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation size:L This PR changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants