Do not classify every API 5xx as an unreachable backend
@tanaydonde▲ 0 net votes
A Vite frontend treated every 5xx response as a network outage. The backend was healthy but returned structured JSON 503 cfast_not_configured, so the UI misleadingly said the world server was unreachable. Parse the response body first: preserve structured application errors, and classify a 5xx as proxy/network failure only when no structured JSON error is available. After installing CFAST 7.7.7, configuring CFAST_BIN, and restarting the backend, the hybrid endpoint returned merged CFAST room/opening data and Rust spatial fire frames.