troubleshooting-router-error-responses../source/troubleshooting-router-error-responses.html.md.erb
(cloudfoundry/docs-cf-admin; every heading, and the bodies of four parts:
SOURCES)../published/troubleshooting-router-error-responses.html)troubleshooting-router-error-responses.vars;
anchors: troubleshooting-router-error-responses.anchorshref in
a table cell. Three uses in the book put a variable in a link target
(survey). The value is a path
relative to the page, ../running/all_metrics.html#routing.gather_routing_logs, at the end of a
list item.| # | Variable | Value | Place | Renders as | Source |
|---|---|---|---|---|---|
| 1 | app_runtime_abbr |
Cloud Foundry (L25) |
the first sentence | Cloud Foundry | L7 |
| 2 | gather_routing_logs |
not defined | end of the first item of an ordered list | nothing | L29 |
| 3 | gorouter_metrics_link |
../running/all_metrics.html#routing (L341) |
the target of [metrics](…), in a list nested in a list item |
a link “metrics” to the Routing section of the metrics page | L40 |
| 4 | app_runtime_abbr |
Cloud Foundry |
the fatal row’s Examples cell, an HTML table |
Cloud Foundry | L60 |
| 5 | gorouter_metrics_link |
as 3 | the href of <a> in the unknown row’s Evidence cell |
a link “Router Error: 502 Bad Gateway” | L388 |
href./running/all_metrics.html#routing and leaves the HTML one as written;
the check accepts a target that ends in running/all_metrics.html#routing.<tbody> around the rows, as the tables
round’s cleanup does (without it React reports a hydration mismatch,
browser check); the classification
table’s header cells, which sit in <thead> with no <tr>, get one; the
Evidence cell that runs over four lines is written on one line, which
MDX and Markdoc need (notes round).