Repository navigation
feat(api): public /api/health with a database check - #600
Merged
Merged
Conversation
GET /api/health answers 200 {"status":"ok","db":"ok"} after one HEAD
select against profiles (3s cap), or 503 {"status":"error","db":"down"}.
Cache-Control: no-store. The proxy lets it straight through so the status
page is never gated, metered or session-refreshed.
For status.profullstack.com, which today only checks the home page.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ThreatCrush Security Scan46 finding(s) HIGH/CRITICAL: 1 | MEDIUM: 7 | LOW: 38
Snippets are redacted; ThreatCrush never prints matched credential material. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
GET /api/healthfor status.profullstack.com (Gatus), which today can only check the home page.{"status":"ok","db":"ok"}after one HEAD select onprofilesvia the existing service client, 3s timeout{"status":"error","db":"down"}on any failure; no error details leakCache-Control: no-storeproxy.tsreturnsNextResponse.next()for this path first, so the check is not gated, metered or session-refreshedWhy it was 404: no route existed.
Verified:
tsc --noEmitclean, eslint clean on changed files,src/proxy.test.tspasses.🤖 Generated with Claude Code