Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connection errors aren't reported to the user #111

Open
tstibbs opened this issue Feb 24, 2014 · 0 comments
Open

Connection errors aren't reported to the user #111

tstibbs opened this issue Feb 24, 2014 · 0 comments
Labels

Comments

@tstibbs
Copy link

tstibbs commented Feb 24, 2014

If I go to something like http://localhost:9200/indexname/_nodes, I get a 400 (bad request) back, and a page with the text No handler found for uri [/indexname/_nodes] and method [GET]. However if I do the same thing through the "Any request" tab of the head plugin, it just says "Requesting..." and never gives me any indication that something has gone wrong (making if difficult to tell if my servers are just being slow or if I've actually got the url wrong). This can also happen if, for example, the server is no longer contactable.

The same applies on the main screen - if the server has gone down, pressing the 'refresh' button achieves nothing. It greys out but it's not really clear what went wrong.

In both cases passing the result of the request back to the user would be useful (at least they know that something has gone wrong, even if they don't understand the error).

@mobz mobz added the Will Fix label Aug 13, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants