Closed timnolte closed 7 months ago
Wanted to supply a sample of the RSS feed in the event that it's some sort of parsing issue, though I suspect an Internal Server Error might imply that this doesn't support query parameters in RSS feeds.
The feed sample is valid. The issue is most likely with cvedetails.com.
I've improved the failed to fetch error message. it now includes the HTTP status code (e.g 404 Not Found). See https://github.com/VerifiedJoseph/vigilant/commit/112800526b7fce8074a8fb8410ff6a3c95cd8913
What kind of headers are being sent when requesting feeds. Because the feed URL works perfectly fine when I use my browser or wget.
Is there a way to get more debugging output logging? ~I have a feeling that the way the code us written is that it is dropping all query parameters from feed URL and that is why it's failing. Has this been tested using feeds with query parameters?~
Actually, I was doing some testing with this RSS testing feed which uses parameters and it was working.
If I run
wget "https://www.cvedetails.com/rss-feed/v1?feedId=###&check=........." -O rss2.xml
I get a valid result.
Resolving www.cvedetails.com (www.cvedetails.com)... 104.18.32.86, 172.64.155.170, 2606:4700:4400::6812:2056, ...
Connecting to www.cvedetails.com (www.cvedetails.com)|104.18.32.86|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [application/rss+xml]
Saving to: ‘rss2.xml’
Doing some searching I'm thinking the issue is that Vigilant isn't actually sending a User-Agent at all perhaps. I found some notes about something like this here: https://developers.exlibrisgroup.com/forums/topic/rss-feed-returning-500-internal-server-error/#post-36468
I ran the RSS feed through the W3C Feed Validation Service and the only thing it flagged was:
This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations. line 6, column 163: Self reference doesn't match document location
Ran wget with some additional debugging output if it will help. It looks like wget does set a User Agent.
https://github.com/VerifiedJoseph/vigilant/pull/109 should, hopefully, address this.
@VerifiedJoseph I just pull the latest changes from main
and manually ran a test and can confirm that this has fixed the issue.
I don't see any option to turn on logging or debugging to get more details. I'm trying to pull feeds from CVE and it's not working. It works just fine via wget/curl/browser.