+1 to that idea... Jay Pipes <jaypipes at gmail.com> wrote on 02/02/2015 04:35:36 PM: > > What about having a separate HTTP header that indicates the "OpenStack > Error Code", along with a generated URI for finding more information > about the error? > > Something like: > > X-OpenStack-Error-Code: 1234 > X-OpenStack-Error-Help-URI: http://errors.openstack.org/1234 > > That way is completely backwards compatible (since we wouldn't be > changing response payloads) and we could handle i18n entirely via the > HTTP help service running on errors.openstack.org. > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150202/dc57a315/attachment.html>