I tried up upgrade to 2.0.5 last night and it went fairly well but not perfectly. I'm still a bit of a NodeRed newbie (though not a programming newbie) and I was hoping you could help me figure out what's wrong.
My most important flow is used to screen scrape a website. It uses my credentials to login then uses the auth cookies to extract info on my behalf. That flow fails under 2.0.5 with a 404 for the POST to the login page.
I run NodeRed in a docker container on my Synology array so I'm a little more limited in watching what is happening, however, in the terminal I was able to watch the NodeRed container start up and I found it was complaining about the https.request code being patched by old code in a dependency. I hunted down what was using that old code, turned out it was speedtest-updated (or something like that) so I removed that node from a flow that used it, removed it from my NodeRed instance, restarted the instance, and verified that I no longer get the warning on startup. That POST still returned a 404.
I then closed that container down and switched back to the container that's running 1.3.4 and I was able to immediately use that flow. I verified that the POST returns a 302 redirect as expected.
What would be the best way to proceed in debugging this?
I grabbed the msg object input and output from the successful POST under 1.3.4 so I was thinking tonight I would start up 2.0.5 again and grab the msg object input and output for the failed POST then see if I can find any difference. I suspect there will not be any difference in the input and the output likely will not be helpful since it'll just be the content of the 404 page.
I tried to install the flow debugger but I couldn't figure out how to do it, or maybe it's already installed and I just don't know how to use it. I suspect in this case it won't help because I know the input to that node is correct, it feels like something is going wrong during the request to the site and I don't know how to dig in that deep to find out nor do I know if there's a way to directly see what the node actually sends to the site to see how it differs between 1.3.4 and 2.0.5.
I could create a very simple repro flow to give to you guys but since it requires credentials to use it I'm not sure how best to package those for sharing (since I obviously won't share a flow with credentials). Clearly I need to learn if there's a way to supply credentials to a flow without including them directly in the flow. Evidence of being a newbie.