6feea1a506
* Update Enterprise Search request handler to send back an error connecting header - vs only distinguishing error connecting issues by 502 status + clarify comment where this.handleConnectionError is called - for the most part, auth issues should already be caught by 401s in logic above * Update HttpLogic to set errorConnecting state based on header + update tests etc to match read-only-mode state * [Tech debt] Gracefully handle invalid HTTP responses I've noticed this error a few times after Kibana gets shut down (http.response is undefined) so figured I would catch it here * Fix missing try/catch/flashAPIErrors on engines overview - This is the only http call I found missing a try/catch across our codebase, so we should be set for all views correctly flashing an API error that receive a 5xx response from ent-search Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| applications | ||
| index.ts | ||
| plugin.ts | ||