archipelagoandClaude Fable 5 ee15626127 fix(appgate): dead upstream serves a named, self-retrying page ...

The gate answered a dead app with the bare string "app is not responding",
which on the app's own port reads as the node itself being broken — reported
against Gitea on a fleet node (the actual fault was a ghost container holding
Gitea's LevelDB lock, crash-looping the managed container). Serve the same
styled page as the login challenge instead: names the app, says it may be
restarting, and retries via a Refresh header (page CSP allows no script).
Status stays 502 so machine clients still see an upstream failure.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-08-10 15:29:19 -04:00

..

testdata

feat(appgate): serve HTTPS and HTTP on the same app port

2026-08-06 15:23:47 -04:00

identity.rs

security: remove all infrastructure and internal process material from the repo

2026-08-07 10:37:20 -04:00

listener.rs

security: remove all infrastructure and internal process material from the repo

2026-08-07 10:37:20 -04:00

mod.rs

fix(appgate): dead upstream serves a named, self-retrying page

2026-08-10 15:29:19 -04:00

tls.rs

feat(appgate): serve HTTPS and HTTP on the same app port

2026-08-06 15:23:47 -04:00