Describe the problem/error/question
The HTTP Request node has stopped working in version 1.6.0 and later, while it was functioning without issues up to version 1.5.1.
I’m attaching an example of a request to the official Polish Post tracking service, which operates based on SOAP.
This request returns information about the status of the package with the number provided in the query. For version 1.5.1, I receive a correct response from the service. However, in higher versions of n8n, there seems to be a problem because the response from the service shows a several-megabyte file in n8n and XML to Json node cannot parse it.
Please share your workflow
Information on your n8n setup
n8n version: 1.6.0 and later
Database (default: SQLite): postgres
n8n EXECUTIONS_PROCESS setting (default: own, main): default
Running n8n via (Docker, npm, n8n cloud, desktop app): docker
Operating system: ubuntu
Can you add a new http request node and set that up with the same config to see if that changes anything? If you can include the full request it will tell us what the response headers are as well so we can take a proper look.
@Jon how can I get full request from http request?
There is an option in the newer node version where you can set the response to include the full response.
Everything is working now that I’ve used the new version of the HTTP node.
Thanks for pointing it out.
Can confirm I had the same issue and was so confused because it was working fine before we upgraded, re-doing the http nodes fixed it for me as well.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.