I am currently interfacing to a system using a REST interface. I also use Postman to do sanity checking on my query strings to verify legit parameters before going to KNIME.
It works on Postman, but Knime does not like this - it throws an “illegalArgumentException” at postion xyz - I traced the position to the characters “>date(2018,7,1)”. Am I doing something wrong - is it a parsing bug, or is there an alternative syntax I should use?
As you can also nicely see by the automatic link conversion of your post, > is not an allowed character in a URL. You have to %-encode the character, in your case %3E. The same may also be true for ( and ) and is certainly true for + because in query parameters it’s a replacement for space.
That won’t help in this case. Here we are talking about correct encoding of the URL whereas your problem was encoding the request body with a specific encoding.
Sorry i remember it was doing both things.
For this specific task i usually build the url (it has a specific sintax) , in this way you dont encode wrong characters like =
You usually need to do this in a java snippet because automatic conversion doesn’t work