Forum Discussion
TanyaYatskovska
SmartBear Alumni (Retired)
Hi Kieron_horide-h,
The issue reported in this thread was fixed in the Ready! API 1.4 maintenance build. Please check if the issue disappears in your case:
kieron_horide-h
10 years agoNew Contributor
Understood. I was thinking this might be a work-around to try, allowing users to stay on the normal upgrade path.
However, the maintenance build doesn't fix my problem - in SoapUI NG, the Raw view of the request shows M?ori ???? in a value, where in the Form view it has Māori ĀĀāā (the header has Content-Type: application/xml; charset=utf-8 ). the request fails server-side validation because of the '?' characters. This problem is resolved by adding -Dfile.encoding=UTF8 to the vmoptions file.
Related Content
- 2 years ago
- 3 years ago
- 3 years ago
- 6 years ago
- 4 years ago
Recent Discussions
- 5 days ago