troubleshoot-app-health and routes-domains: one partial on two pages../source/troubleshoot-app-health.html.md.erb
(section “Routing conflict”, lines 146–165) and the headings round’s
routes-domains
(section “Map a route to multiple apps”, lines 404–408); the partial
_routing_conflict;
cloudfoundry/docs-dev-guide../published/troubleshoot-app-health.html)
and the headings round’s routes-domainstroubleshoot-app-health.partials,
routes-domains.partials; anchors:
troubleshoot-app-health.anchors,
routes-domains.anchors<%=vars.product_short%>, and a partial file without a final newline.routes-domains (<h4>), which
the headings round’s convention writes as the tool’s heading.| Page | Section | Place | After the host’s words | Before the host’s words |
|---|---|---|---|---|
| troubleshoot-app-health | Routing conflict | body | the heading | “If you suspect a routing conflict” |
| routes-domains | Map a route to multiple apps | body | the heading | “For more information about troubleshooting this problem” |
The partial opens with “Cloud Foundry allows multiple apps, or versions of the same app” (the variable’s value) and ends with “to one of the apps on the shared route.”
None. The links in the partial and on routes-domains lead outside the
excerpts; tools that check links report them.