RQM CommandLine Adapter, Encoding of Uploaded File
I'm using the RQM commandline adapter to execute tests. The test result is uploaded by the commandline adapter to RQM and is attached to the execution record. The result file is an UTF-8 encoded (content="text/html; charset=UTF-8") html file.
If I open the file directly by clicking on the link in execution record, a wrong encoding is used (windows-1252) messing up the design. If I save and open the file the correct encoding is used.
Opening the file directly from RQM ssems to override the defualt document encoding. How can I change this behaviour? Can I specify the desired encoding in the CommandLine adapter?
BR
ollej
One answer
Comments
Thanks for your anwer, Mehul.
The encoding information as specified in the file itself is preserved. The problem is not browser specific.
The problem seems to be that when clicking on the file link in RQM the http response of the RQM Server on the get request of the browser has the content type information ISO 8859-1 which overrules the file encoding (in my case UTF-8).
So the real question is, why does the server specify its response with this encoding and how can I change it? As I see it, the server should either specify the correct encoding in the reponse content type or not content type at all, so that the browser would choose the document encoding for displaying it. Can I influence this behaviour?
Regards
Oliver
Hi Oliver,
Normally if your QM database is using
codeset UTF-8, the server would not change the encoding.
If you run a GET command via Poster or REST client on the file link, which encoding do you get?
Cheers,
Will