docs(3189): the error-page scope text describes the new shape
Two claims this branch falsified and left standing, both caught in
review:
`vhosts.nix`'s `errorPages` param comment enumerated the set
(`{ notFound, unreachable, unauthorized }`) and adding a fourth member
made the enumeration wrong at the point a reader consults it.
`gateway.md` said extending custom error pages beyond the per-agent
routes was "a separate follow-up" — while this branch is that follow-up,
so the doc contradicted the code sitting next to it.
Rewrites the scope rule as the criterion rather than a list, since a
list is what went stale: a route earns a page when the default status
would point at the wrong component. That covers the per-agent routes and
the sso vhost, and explains why forge/matrix/fluffychat still don't
qualify — their upstreams being down means what the code says.
This commit is contained in:
parent
275d502639
commit
ac15c68cd2
2 changed files with 11 additions and 5 deletions
|
|
@ -477,10 +477,16 @@ palette (`#1e1e2e` bg, `#cdd6f4` text, `#cba6f7` heading). No
|
||||||
dependencies on the frontend dist — these pages render even when
|
dependencies on the frontend dist — these pages render even when
|
||||||
hive-c0re itself is down.
|
hive-c0re itself is down.
|
||||||
|
|
||||||
Scope is intentionally narrow: only routes already special-cased in
|
Scope is intentionally narrow: a route earns a custom page when the
|
||||||
the nginx config get custom error pages. Other gateway routes
|
default status code would point at the wrong component. The per-agent
|
||||||
(forge / matrix / fluffychat) get nginx defaults — extending the
|
routes qualify (a 502 there means the harness is restarting, not that
|
||||||
custom-error pattern there is a separate follow-up.
|
the gateway is broken), and so does `auth.<swarm>` — a dead authelia
|
||||||
|
upstream almost always means the user store was never bootstrapped, and
|
||||||
|
a bare 502 blames the proxy, which is the one part that is working.
|
||||||
|
|
||||||
|
Forge / matrix / fluffychat still get nginx defaults: their upstreams
|
||||||
|
being down means what the status code says, so a themed page would add
|
||||||
|
styling and no information.
|
||||||
|
|
||||||
## HTTP Basic auth
|
## HTTP Basic auth
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -13,7 +13,7 @@
|
||||||
hyperhiveDomain,
|
hyperhiveDomain,
|
||||||
dashboardDist,
|
dashboardDist,
|
||||||
swaggerUiTheme, # nix/packages/swagger-ui-theme.nix: has index.html + hyperhive-theme.css
|
swaggerUiTheme, # nix/packages/swagger-ui-theme.nix: has index.html + hyperhive-theme.css
|
||||||
errorPages, # ./error-pages.nix: { notFound, unreachable, unauthorized }
|
errorPages, # ./error-pages.nix: { notFound, unreachable, unauthorized, ssoUnavailable }
|
||||||
tlsCert,
|
tlsCert,
|
||||||
tlsKey,
|
tlsKey,
|
||||||
svcCert, # swarm-services leaf, for names the hive CA cannot sign
|
svcCert, # swarm-services leaf, for names the hive CA cannot sign
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue