Support Accept-Language for API messages
Currently, error messages coming back from the API are translated using the same locale as the system the API is running on. Ideally, we would like to have the messages translated to the request senders locale, which we can support using the HTTP Accept-Language header to determine before sending back the translated response. Alternatively, there is the possibility of using the tenant/user data from Keystone to store a preferred locale.
There is a similar blueprint for Nova that can be used to track the implementation work there:
https:/
Blueprint information
- Status:
- Complete
- Approver:
- gordon chung
- Priority:
- Low
- Drafter:
- Mathew Odden
- Direction:
- Approved
- Assignee:
- Brad Pokorny
- Definition:
- Approved
- Series goal:
- Accepted for havana
- Implementation:
-
Implemented
- Milestone target:
-
2013.2
- Started by
- gordon chung
- Completed by
- gordon chung
Related branches
Related bugs
Sprints
Whiteboard
I think we could use the Pecan library's 'hooks' mechanism to capture Exceptions and translate the inner messages before returning/
Gerrit topic: https:/
Addressed by: https:/
Add support for API message localization
Addressed by: https:/
Add support for API message localization
Addressed by: https:/
Sync gettextutils from oslo
Addressed by: https:/
Sync gettextutils from oslo-incubator
Addressed by: https:/
Sync gettextutils from oslo-incubator
Addressed by: https:/
Enhance delayed message translation when _ is imported
