TotallyInformation
commented
7 years ago This is still happening - anyone any ideas?
It is preventing me from developing a solution for aggregating feeds.
Closed TotallyInformation closed 6 years ago
TotallyInformation
commented
7 years ago This is still happening - anyone any ideas?
It is preventing me from developing a solution for aggregating feeds.
hardillb
commented
7 years ago Worth testing with the follow-redirects node in play as that's what the httprequest node actually uses under the covers. (https://github.com/node-red/node-red/blob/29cae9975ec27a8b4f2e84a3556ce287e507fdf9/nodes/core/io/21-httprequest.js#L20)
var https = require("follow-redirects").https;
It's all working properly on Linux, so I can only guess that it's something that's being handed off to some Windows system library for some reason.
TotallyInformation
commented
7 years ago Thanks. I'm bored with defining glossary entries and requirements for my work programme so I'm going for some light relief by doing some hacking of the node to see if I can work it out. I will check your suggestion. It used to work but stopped sometime around the start of the year I think. Just never got round to trying to fix it. I suspect the http request node has the same problem. Again though, only on Windows 10 which is strange.
TotallyInformation
commented
7 years ago I've not made much progress but I have discovered that it is a problem with using the "request" module https://www.npmjs.com/package/request
The strange thing is that if I create a simple test js file to call that module (it is in the same folder as the node so I know for sure I'm using the same version, it works absolutely fine. But when called from within Node-RED, it fails.
I've also found out that it is the request module and not the feedparse module that the error is coming from. About line 29 of 32-feedparse.js I think.
But I've not been able to find what is generating the error in the request module. As I say, it works fine if I do this:
var request = require("request");
var req = request('https://www.techdirt.com/techdirt_rss.xml', {timeout: 10000, pool: false});
req.on('error', function (e) {
console.error(e);
});
req.on('response', function (res) {
console.log(res.statusCode);
console.dir(res.headers);
});That is pretty much the same code as in 32-feedparse.js so I can only think that it is something environmental to Node-RED that causes it.
My knowledge of JavaScript debugging is about at it's limit now so I'll have to give up.
I have 2 feeds that work and 1 that doesn't. I'm stuck now.
dceejay
commented
6 years ago seems to be working fine with latest request module
On Windows 10 latest build with Node.js v6.11.0 and NR v0.17.4, Feedparse fails to connect to a feedburner feed using https:
That works fine manually and in other feed readers. The error that is generated is:
On the console:
This appears to be another example of the wildcard altnames issue that has been seen with one or two other nodes.
The HTTP request node does the same thing with any endpoint that uses wildcard certificates that browsers consider valid - e.g. my own blog at https://it.knightnet.org.uk - which uses CloudFlare.
I thought it might be an upstream issue but the following node.js code works just fine: