The error message from the REST API for attempting an unauthorised action gives:
{
code: "401 Unauthorized"
message: "This server could not verify that you are authorized to access the document you requested. Either you supplied the wrong credentials (e.g., bad password), or your
browser does not understand how to supply the credentials required.<br /><br />↵↵↵"
title:"Unauthorized"
}
This is wrong for several reasons:
1) "401 Unauthorized" is not an error code, its an error code converted to a string and with the
error name/title appended.
2) The error message contains "<br /><br />↵↵↵".
3) This part is unlikely to be fixed, but the error itself is not embedded in an error object as
with Keystone and Neutron, so the consistency issue means a generic solution can't be used.
The error message from the REST API for attempting an unauthorised action gives:
{
requested. Either you supplied the wrong credentials (e.g., bad password), or your "Unauthorized"
code: "401 Unauthorized"
message: "This server could not verify that you are authorized to access the document you
browser does not understand how to supply the credentials required.<br /><br />↵↵↵"
title:
}
This is wrong for several reasons:
1) "401 Unauthorized" is not an error code, its an error code converted to a string and with the
error name/title appended.
2) The error message contains "<br /><br />↵↵↵".
3) This part is unlikely to be fixed, but the error itself is not embedded in an error object as
with Keystone and Neutron, so the consistency issue means a generic solution can't be used.