The solution of that one was to use the Palladian http-nodes, which I can confirm acts as a workaround to the issue in the Analytics Platform. However, that is not a solution for the KNIME Server we are running, where I’d like to use standard nodes as much as possible.
You’re getting a JSON content type in postman but a text/plain type in KNIME? Have you specified an Accept header? If so you could try removing this or setting it to application;json; charset=UTF-8 or something similar.
that’s an interesting issue. A small observation- it seems that your situation differs from the thread that you’ve linked at the beginning- they got an missing body (the red question mark), while you get the body not displayed (blank white space).
Could you try to dump the resulting table into a file to check if the cell has any contents? And maybe check what does the “Spec” tab show for the possible values in the body column. I wonder if maybe the problem is not with wrong type of returned payload, but rather with displaying the content, similar to what has been observed in Problem while concatenating via the GroupBy node Value 0 ?
I tried the suggestion from Problem while concatenating via the GroupBy node Value 0 by copying + pasting the contents into a text editor (Notepad++ or normal Notepad) and can confirm that it’s completely empty (not even a space). So it seems to be something else in this case.
As a workaround, I just installed Anaconda Python on my KNIME Server & my laptop running the KNIME Analytics Platform, and then used the “requests” package to do the work for me (like shown here: Delete Request with body). That way I can work with KNIME Server again (even though I’m not completely happy with this solution).
I don’t think this is related to the issues they people had above. Is the link working when you send a GET request? I tried and the body wasn’t empty. Also when you try the link online it has content.
Could you please share an example that isn’t working please? Sometimes, and I think this is also happening here, the WebServices don’t have any data to provide and then the body is empty and contains a red question mark.
has there been any update on this issue recently?
I am experiencing exactly the same problem (empty body with status 200) with the POST Request node.
However, in my case this seems to appear only if I receive a “larger” amount of data from the webservice. (where “larger” is something like >1024 characters or so)
If I query a smaller dataset from the webservice, it works.
Oh, what a coincidence…
We are currently using KNIME 4.0.2 because we need NTLM authentication and there is obviously a bug with NTLM in 4.1. Do you have any information if that bug still persists in 4.2?