I have created an HTTP request to the URL below in SoapUI (v5) and SoapUI Pro NG (ReadyAPI v2.0):

http://localhost:8888/content-service/content/book?query=(collection="book title")

However, the encoding of the URL sent appears to differ between the two. It looks like SoapUI is encoding the quotes to %20 and %22 respectively.

In SoapUI Pro NG it seems to be encoding the URL twice, converting the % to %25 followed by the 22, resulting in %2522.

Why do the free edition and the paid edition have different encoding behaviours?

Sent using SoapUI Pro NG:

GET http://localhost:8888/content-service/content/book?query=(collection=%2522book%title%2522) HTTP/1.1
Accept-Encoding: gzip,deflate
Host: localhost:8888
Connection: Keep-Alive
User-Agent: Apache-HttpClient/4.5.2 (Java/1.8.0_112)

Sent using SoapUI:

GET http://localhost:8888/content-service/content/book?query=(collection=%22book%20title%22) HTTP/1.1
Accept-Encoding: gzip,deflate
Host: localhost:8888
Connection: Keep-Alive
User-Agent: Apache-HttpClient/4.1.1 (java 1.5)

I have tried disabling URL encoding and putting in %20 or %22 but this results in the reverse behaviour occurring.

  • also raised with SmartBear support community.smartbear.com/t5/SoapUI-NG/…
    – ECiurleo
    Commented Jul 20, 2017 at 13:46
  • 1
    Investigation so far indicated endpoints and query follow different encoding patterns. Will update further as I work out more
    – ECiurleo
    Commented Jul 26, 2017 at 7:07

1 Answer 1


I appear to have discovered the issue.

A REST GET request to a URL using SoapUI follows different encoding rules to an HTTP GET request.

Smartbear were unable to provide a reason for the difference in behaviours

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.