vjeka1 commented on issue #62697:
URL: https://github.com/apache/airflow/issues/62697#issuecomment-3983868281
Turns out it was a nginx location rule on our side:
location ~ "/(ping|health)" {
return 200;
}
This rule is meant for infrastructure health checks, but it also matches
`/airflow/api/v2/monitor/health` — so the proxy was returning an empty
`200 OK` instead of forwarding the request to Airflow. Our bad!
That said, I still think the `Health.tsx` fix makes sense regardless.
A proxy misconfiguration, a network hiccup, a timeout — there are many
reasons the health endpoint might return nothing, and the page shouldn't
crash when that happens. The `<ErrorAlert>` is already there for this,
it just never gets to render because the crash happens first.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
