You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
If I go to something like
http://localhost:9200/indexname/_nodes
, I get a 400 (bad request) back, and a page with the textNo 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).
The text was updated successfully, but these errors were encountered: