Forum Discussion

mmoser18's avatar
mmoser18
Frequent Contributor
4 years ago

SOAP-UI Mock: Response in different character sets on different systems - WHY?

I have the odd case that a mock service that I defined works as intended on one system but not on another (both are Windows 10 workstations/laptops running the same version, configured with the same ...
richie's avatar
richie
Community Hero
Hey,

You mightve already confirmed this so apologies if you hVe, but have you compared the system properties of both instances?

I.e. Help >> System Properties

Id compare these. I know theres an emcoding/charset attribute in there somewhere that might help....

Cheers

Rich
mmoser18's avatar
mmoser18
Frequent Contributor
4 years ago

We compared our System Properties. The only - in this context - possibly relevant difference is the file.encoding setting (UTF-8 in my case and Cp1252 on my colleague's machine). But the READING from file is not the issue here. The bytes read are identical (the script displays them in the log output - see line

log.info("read ${length} bytes of data: '${fileBytes}'"

... and at that point the bytes are exactly identical (i.e. identical values and correct byte ordering (according to UTF-16LE)).

 

It must be something that affects the SENDING of the response content and thereby mangling the character encoding.

  • richie's avatar
    richie
    Community Hero
    4 years ago
    Hey mmoser18,

    I appreciate what you stated about something altering the sending of a response however a colleague had an issue that was analgous to yours, hence why i queried the default encoding.

    When you say it runs differently on two machines, how were the readyapi! projects setup on each machine? Created in one, then a copy sent to the other machine? If thats not the case then the mocks were setup independently? If yes.......

    To attempt to fix: export the project that works and import overwriting the project on the machine that doesnt work.
    If this doesnt resolve the issue, then logically the issue is not at project level, its global/workspace level and id look at the differences in system properties as surely its reasonable that this could be the cause of the issue? Unless youve got a dodgy event handler running...

    Ta

    Rich
    • mmoser18's avatar
      mmoser18
      Frequent Contributor
      4 years ago

      The project was carried over (via the same git-repo) and are identical.

      SOAP-UI was installed on both systems using the vanilla installer.

      No event handlers or other hooks were added.

       

      I fail to see how any system settings could interfere here since the handling of the response is entirely done inside SOAP-UI. It reads the file (at which point the data are correct) and then converts the response to the response's payload and serves that via the built-in mockserver. So, "something" must be telling SOAP-UI to convert (or keep) the payload-string to/in UTF-16LE on my machine and to convert it ISO-8859-1 along the way on my colleague's system.