Actions
Bug #3828
closedAPI messages and error responses not in English
Description
The error responses from the API are often shown in languages other than English, seemingly random. For example:
Started POST "/api/smart_proxies" for 10.35.160.133 at 2013-12-05 17:01:27 +0200 Processing by Api::V1::SmartProxiesController#create as JSON Parameters: {"smart_proxy"=>{"url"=>"https://example.redhat.com:9090", "name"=>"example.redhat.com"}} Authorized user admin(Admin User) Unprocessable entity SmartProxy (id: new): No ha sido posible establecer una comunicación con el proxy: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed Por favor, comprueba que el proxy está configurado y ejecutándose en el equipo
I suspect we're not initialising the current locale correctly in the API controllers, while we do in the UI controllers based on the user.
Updated by Joseph Magen almost 11 years ago
- Status changed from New to Assigned
- Assignee set to Joseph Magen
Updated by Joseph Magen almost 11 years ago
- Status changed from Assigned to Ready For Testing
Updated by Dominic Cleal almost 11 years ago
- Translation missing: en.field_release set to 2
Updated by Anonymous almost 11 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 5a864bedb5d9bbbb68788169aa0f0396a312ac16.
Updated by Lukas Zapletal over 10 years ago
- Related to Bug #6824: Internationalization does not work when setting the preferences to use the Browser locale added
Actions