| 2013-09-24 22:31:00 |
Luis A. Garcia |
description |
Unlike error that result from HTTPExceptions, the error responses that result from CinderExceptions are not being translated anymore.
To reproduce an example:
Try the following request:
POST /v2/{tenant-id}/snapshots
Body:
{"snapshot": {"volume_id": "99"}}
Headers:
Accept-Language: es (or some language installed)
Content-Type: application/json
This will result in the following:
{
"itemNotFound": {
"message": "VolumeNotFound: Volume 99 could not be found.",
"code": 404
}
}
That is, an English response (or the default locale's) even if the requested locale is available. |
Unlike error that result from HTTPExceptions, the error responses that result from CinderExceptions are not being translated anymore.
To reproduce an example:
Try the following request:
POST /v2/{tenant-id}/snapshots
Body:
{"snapshot": {"volume_id": "99"}}
Headers:
Accept-Language: es (or some language installed)
Content-Type: application/json
This will result in the following:
{
"itemNotFound": {
"message": "VolumeNotFound: Volume 99 could not be found.",
"code": 404
}
}
That is, an English response (or the default locale's) even if the requested locale is available.
PS: Invalid and NotAuthorized CinderExceptions are handled correctly |
|
