Forum Discussion
I can't really post my full reponse here from the HTTP log. It does come back in escaped values, shown here.
The RAW view in the response test step also will not let me scroll to copy the entire raw response. So, the error in question is too far over, and readyapi won't let me scroll over to see it.
Have you checked with you team regarding this?
Also there is header "Content-Encoding" header with gzip.
Are you sending any header related to this?
Also check the documentation below if you have preferences set to receive compressed response . Try changing it in case needed.
https://www.soapui.org/docs/preferences-and-settings.html#HTTP-Settings
- richie5 years agoCommunity HeroHi tadudek,
It looks like Rao's got the right idea. Your response is being served gzip compressed which is why it looks a mess.
I think you have a choice here. You can either change the Accept-encoding header value on request to remove gzip (which can work, but not always...depends om server), OR
There's a checkbox on the http settings Rao pointed you to...'accept compressed response from host', you could disable this. I think the label of the checkbox is a little misleading...i read this like it means soapui cant receive compressed responses but the help thats been published reads like it decodes compressed responses.
Also you previously mentioned non utf-8 valid characters and CDATA in your response. If this is still relevant you can use an event handler to strip out CDATA tag handlers and non utf-8 characters on a response meaning ReadyAPI!'s xml parser will be able to successfully read the data in response.
Finally, in regards to not being able to view all of a response in your RAW tab, you can highlight some of the text in the RAW tab, grab it, copy and paste it out so you can view all detail in RAW if necessary.
Cheers
Rich - tadudek5 years agoOccasional Contributor
Frankly, this was taking way too long, and with all the craziness in the world, I can't spend any time on it right now. I went back the long (and tedious) way, and changed my groovy datasink back to an excel data sink, and now need to manually map xml nodes back to excel row-cells. (This really doesn't do what I want it to do, but it'll do for now.)
I created an enhancement request for the excel datasink, because it forces you to map recurring elements, which is weird.
And from a groovy perspective, there just isn't enough documentation on the groovy datasink to best do what I would like to do. I feel like I'm doing too much guessing.
I'll follow up next week with some attempt at the communities changes. Thanks -tadudek