-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UTF-8 characters are unescaped even if they were escaped in response #745
Comments
What version of rest assured are you using? |
3.0.0 |
Hmm... It's strange that you also get the same problems if you use Jersey. Could it be a JVM setting? I always start my JVM with |
I usually run my tests from IDEA, and I don't know what settings it uses, but I specified that option in run properties, and I got the same as previously. |
Ah ok then I misunderstood you. Isn't the server also returning a charset? What does wireshark show you? |
Just checked: server is returning charset UTF-8 |
Hmm ok, I'm not sure what to make of this. Maybe it's the JVM that does this automatically?! |
Then it's strange that SoapUI shows it differently, as it is a Java application. Do you know how to check if it's JVMs fault? |
Ah OK, I confused SoapUI with Postman. Then I'm not sure what could be the cause of this. Something with Apache HTTP Client perhaps? |
Is there a way to check? I would post them a bug if it's their issue. |
The only way I can think of to check this would be to try to make the same request using vanilla Apache Http Client. |
I have a service that returns an xml containing, among others, value
CALLE MARÍA LOZANA
, but in prettyPrint() I seeCALLE MARÍA LOZANA
. And object I get from response via JAXB also hasCALLE MARÍA LOZANA
for this field. But every other http client (postman, soapUI, curl) show escaped symbol (Í
, notÍ
). So, what restassured shows happens to be different from what there really is. The my service's behaviour is definitely a bug, so I need to see such things and to be able to check for them, and that is impossible with restassured unescaping things that are escaped.For those who might think that problem is in other clients: there is another service that returns values with diacritic signs, and for that service all http clients (postman, soapUI, curl) show that symbols are not escaped.
The text was updated successfully, but these errors were encountered: