Clearer error message for mismatched kbn-version on api request #6021
Labels
enhancement
New value added to drive a business result
Team:Core
Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Comments
epixa
added
bug
|
See the discussion starting at #5213 (comment) for a real world example of this confusion. |
Merged
|
I just faced this issue and I also think the error message could be clearer. This let to think that the UA might come into play, even though it's not. |
milutz
added a commit
to samtecspg/conveyor
that referenced
this issue
Aug 16, 2018
This is calebes find, based from elastic/kibana#6021 and then searching our source - This all came from me trying to change ES version and then getting the 'Browser client is out of date, please refresh the page' error in our stuff, and confused by it (thinking it was our version checking, not realizing it was a misleading error message from elastic
timroes
added
Team:Core
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you make an API request to Kibana (e.g. the new ingest API) with an outdated kbn-version header, you get the error
Browser client is out of date, please refresh the page. This error message is extremely useful when a user experiences while using Kibana in their browser, but it's misleading and unhelpful when encountered when trying to make an API request. We should either make the error message dependent on context or make it general enough to apply to any context.The text was updated successfully, but these errors were encountered: