Bug 862781 - [RFE] [RESTAPI]: missing encoding charset in api json responses
[RFE] [RESTAPI]: missing encoding charset in api json responses
Product: oVirt
Classification: Community
Component: ovirt-engine-api (Show other bugs)
Unspecified Unspecified
medium Severity unspecified
: ---
: 3.5.0
Assigned To: Ori Liel
: FutureFeature, Triaged
Depends On:
  Show dependency treegraph
Reported: 2012-10-03 10:14 EDT by Gal Leibovici
Modified: 2016-02-10 14:30 EST (History)
11 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2014-02-26 08:04:41 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: Infra
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Gal Leibovici 2012-10-03 10:14:00 EDT
API responses are missing encoding info in HTTP header Content-Type.
It should have a charset value with the encoding of the response body.

For Example: Content-Type: "application/xml; charset=UTF-8"
Comment 4 Juan Hernández 2013-10-10 12:34:37 EDT
I submitted a patch that modifies the application so that it will add the charset to the Content-Type header:


The result is something like this:

  HTTP/1.1 200 OK
  Date: Thu, 10 Oct 2013 15:37:34 GMT
  Server: Apache/2.4.6 (Fedora) OpenSSL/1.0.1e-fips
  Pragma: No-cache
  Cache-Control: no-cache 
  Expires: Thu, 01 Jan 1970 01:00:00 CET
  Content-Type: application/json;charset=UTF-8
  Vary: Accept-Encoding
  Transfer-Encoding: chunked

However it isn't clear to me if we want to do this for JSON (as in the subject of the bug) or for XML (as in the initial descrition) or for both.
Comment 8 Juan Hernández 2014-02-17 11:51:31 EST
The solution in comment 4 has been rejected.
Comment 9 Ori Liel 2014-02-26 08:04:41 EST
Resteasy does not provide a way to dynamically set charset in the response. Only 'hard-coded' solutions seem possible, and since a hard-coded solution has already been rejected (http://gerrit.ovirt.org/20104), we're stuck. It seems not worth the effort at this point.

Note You need to log in before you can comment on or make changes to this bug.