Forum Discussion
richie
Community Hero
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
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
4 years agoFrequent Contributor
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.