Forum Discussion

biiincheeen's avatar
biiincheeen
Occasional Contributor
13 years ago

Option to switch off encoding of parameters itself

Dear Soapui Team, I would really wish to have an option to switch of the %-encoding of the parameter values. My case is as follows: I am testing a OData service with the REST service funktion. ODa...
SmartBear_Suppo's avatar
SmartBear_Suppo
SmartBear Alumni (Retired)
11 years ago
The best workaround I found for including unencoded special characters is included in the attached image. Even though I checked "Disable Encoding" we still have issues with sending unencoded spaces. For that, I did not yet find a workaround. Let me know if that's a blocking issue.
For "$filter" and question mark, we can send that parameter name in a resource section of a REST request, instead of a query string. That's highlighted in the attached image.
I've been able to make these values dynamic with a TEMPLATE style parameter as described here - http://www.soapui.org/REST-Testing/unde ... parameters
Do note that I had to include a dollar sign twice, since ${} format is used for our property expansion syntax - http://www.soapui.org/Scripting-Propert ... nsion.html

Thanks,
Michael Giller
SmartBear Software
  • Lureck's avatar
    Lureck
    Frequent Visitor
    8 years ago

    Thanks for the workaround.

    Well unfortunatly it looks like it does not work any longer in Ready!API 1.7.0
    If I follow your hints, in the end all resource parameter disapear in the request uri.

     

    Are there new hints that I did not find yet, how to use OData $search= with spaces in the URL ?