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
{{ message }}
This repository has been archived by the owner on Jul 6, 2023. It is now read-only.
Same applicable for cluster/device/node
#heketi-cli cluster info t
Error: 404 page not found
# heketi-cli device info t
Error: 404 page not found
#heketi-cli node info t
Error: 404 page not found
When a path with an illegal id is provided by the caller (something
that does not match the regexp), the Gorilla Mux Router automatically
routed the call to http.NotFoundHandler(). This would be ok for
an API to handle, but the heketi-cli would output information which
was not very human friendly.
Instead, we now provide our own error handler which returns a nicer
error than just "404: Not found".
Closesheketi#539
Signed-off-by: Luis Pabón <lpabon@redhat.com>
When a path with an illegal id is provided by the caller (something
that does not match the regexp), the Gorilla Mux Router automatically
routed the call to http.NotFoundHandler(). This would be ok for
an API to handle, but the heketi-cli would output information which
was not very human friendly.
Instead, we now provide our own error handler which returns a nicer
error than just "404: Not found".
Closesheketi#539
Signed-off-by: Luis Pabón <lpabon@redhat.com>
BZ 1351646
The text was updated successfully, but these errors were encountered: