SoapUI 3.6.1 request params with pipe character
In SoapUI 3.6.1, when I have a test step that creates an HTTP or REST request with a parameter whose value contains pipe characters (a.k.a. vertical bar, or "|"), instead of passing the value to the server as-is, it splits the value at each pipe character and repeats the parameter that many times in the request. For example, if I specify a parameter color=brown|blue|green, then the request that gets sent to the server is http://localhost/?color=brown&color=blue&color=green. Note that the same thing happens when posting the request parameters using the "Post QueryString" checkbox. This only happens SoapUI 3.6.1, the latest release. SoapUI 3.5, 3.5.1, and 3.6 do not behave this way.
It looks like SoapUI tried to get clever and add a feature for specifying multi-valued request parameters. The problems with this implementation are that:
1) It breaks all of our current tests because we expect the "|" in the request parameter value to be passed to the server, and
2) There appears to be no workaround because if I change the characters to the URL-encoded equivalent (i.e. if I use "%A6" instead of "|" in the value), then SoapUI tries to be helpful and URL-encode the "%" character before sending the request to the server.
I've attached a small sample SoapUI project that demonstrates the described behavior. Please fix this bug or advise of a way to disable this behavior. Thank you.
It looks like SoapUI tried to get clever and add a feature for specifying multi-valued request parameters. The problems with this implementation are that:
1) It breaks all of our current tests because we expect the "|" in the request parameter value to be passed to the server, and
2) There appears to be no workaround because if I change the characters to the URL-encoded equivalent (i.e. if I use "%A6" instead of "|" in the value), then SoapUI tries to be helpful and URL-encode the "%" character before sending the request to the server.
I've attached a small sample SoapUI project that demonstrates the described behavior. Please fix this bug or advise of a way to disable this behavior. Thank you.
