Forum Discussion

mbennett20001's avatar
mbennett20001
New Contributor
12 years ago

Mis-interpreted UTF-8 characters in XML response view

I have registered a simple REST service in SoapUI 4.5.0. If the response contains a multi-byte utf-8 character, the "XML" response view does not show the proper corresponding utf-8 character. Instead it shows the same as the "RAW" response view. Screenshot attached. Also note the http log showing the actual response. Is this a bug or do i need to configure soap ui to render using utf-8 somewhere?
  • mbennett20001's avatar
    mbennett20001
    New Contributor
    12 years ago
    Here's the same XML response viewed from Chrome.
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    12 years ago
    Glad to hear this works! Sometimes UTF-8 characters will not render correctly in SoapUI but should still be encoded correctly in the message.

    Also in most cases the following option corrects the issue:
    File > preferences > UI Settings tab > check "Native LF"
    (Restart SoapUI)

    Michael Giller
    SmartBear Software
    • asn_007's avatar
      asn_007
      Contributor
      8 years ago

      I think I have a similar problem but have tried all other options including above but still no luck.

       

      I created  an XML using groovy and passed that request xml to the SOAPUI Request Tab.

      I am actually trying to send this xml to a JMS queue and have configured the HermesJMS to connect to queues.

       

      But I hit the submit button to send the request to the queue, my application log throws an error below :

       

      <Number>0x00030001</Number>
      <Text>illegal character 'R' at offset 0 of dpmq://dpmq_Eai/fsh_MQ_<MyServiceName>?RequestQueue=<QueueName></Text>
      </RecoverableException>

       

      When I hit CTRL+S to save the above xml to my local and then post this xml file using RFHUTILC< my application does not throw any error.

      Not sure what is different between the Request tab sending it and the file being sent directly tot he queue.

       

       

       

      • groovyguy's avatar
        groovyguy
        Community Hero
        8 years ago

        You may want to start a new thread for your problem. You replied to one that is over 4 years old.

  • Debz's avatar
    Debz
    Contributor
    8 years ago
    I thought it's just on encoding. There are several header options in SoapUI nowadays. Some are for authentication bypass, tokens, etc. I agree with groovyguy, it might be better to start a new thread for this one so that you can also add some tags for other specialists to see. Then add more details like at least a portion of the request xml which you think threw this error and a longer portion of the error log. Other community members here are good at analyzing or interpreting those logs. They might be able to help you debug ;-)