Fix timeout middleware panic on proxy/WebSocket routes and worker healthcheck

Browse Source

The TimeoutMiddleware wraps the response writer in *http.timeoutWriter which
doesn't implement http.Flusher. When the admin reverse proxy or WebSocket
upgrader tries to flush, it panics and crashes the container (502 Bad Gateway).
Skip timeout for /admin, /_next, and /ws routes.

Also fix the Dockerfile HEALTHCHECK to detect the worker process — the worker
has no HTTP server so the curl-based check always failed, marking it unhealthy.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

...

This commit is contained in:

Trey t

2026-03-02 19:56:12 -06:00

parent 7690f07a2b

commit 7438dfd9b1

8 changed files with 12 additions and 1 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

0

docs/go_to_prod.md → docs/GO_TO_PROD.md

0

docs/# Full Localization Plan for Casera.md → docs/LOCALIZATION_PLAN.md

0

docs/Secure Media Access Control.md → docs/SECURE_MEDIA_ACCESS.md

0

docs/COMPETITOR_ANALYSIS.md → docs/marketing/COMPETITOR_ANALYSIS.md

0

docs/PRESS_RELEASE.md → docs/marketing/PRESS_RELEASE.md

0

docs/SOCIAL_MEDIA_KIT.md → docs/marketing/SOCIAL_MEDIA_KIT.md