Forum Discussion
Quick question...when you say "deal with", what do you mean by this?
Secondly REST rules state the sequence in which your Query parms appear in your URI string doesn't matter....i.e. your endpoint should deal with the request no matter what order your query parms are in. With this in mind, are you sure you need to "deal with" the repeated query parm in a nonsequential order?
Cheers,
Rich
The following instructions aren't as clear as they could be:
Step 1: "in Resource or in Method, add parameter (use style = QUERY)" = Is fairly straight forward. I'm choosing "Method", but perhaps I should choose "Resource"?
Step 2: "select parameter and enable "Disable Encoding" at bottom of page" = Is fairly clear. Does this need to be done with each duplicate. Also, how does SoapUI know where to insert each duplicate property within the urlencoded string (see Step 5)
Step 3: "in Request, select parameter and set Multi-Value Delimiter to \| in bottom-left properties section" = Is clear with backslash pipe (\|)
Step 4: "Set a value of, e.g., 1|2|3 for the parameter (can use DataGen)" = Is not clear on whether DataGen is needed and under what circumstances
Step 5: "Request will be sent out with, e.g., parameter=1¶meter=2¶meter=3" - Is a clear example of duplicate properties of the same exact name being used "back-to-back", but not for one where duplicate properties are spread throughout a string where they're separated by other properties. Also, SoapUI does not allow duplicate property entries (see attached screenshot) of the exact same name. It also does not mention whether duplicate properties, after the initial one, need to have a character in its name be replaced with a HTML Hex Code or not. For example, REMARKS, REM%41RKS.
Related Content
Recent Discussions
- 4 days agominhng