fogleman
URL Validation issue
If I provide a private url which is on https with a custom port then the Invalid Feed prompt is displayed. The example url is
https://someurl.com:8050/somepage/morepage/rss
Edit: I wanted to let you know that this url is actually a Jenkins system which requires authentication. I don't know if that is a feature in your app. If it is then it is only the url validation issue else it might be authentiation as well.
On some further investigation, I am inclined towards thinking that it has to do with the certificate being used. This is a custom certificate generated for this web instance. I believe view.py#196 is the culprit. It is not able to go through or sniff the custom certificate and hence is throwing exception. I am not a python developer but I want this tool to work and hence went in to look myself.
On further analysis, I found that following is the culprit. It is returned from the feedparser.parse module and since the status is 403, the code returns the invalid feed message.
{'bozo': 1, 'bozo_exception': NonXMLContentType('text/html;charset=UTF-8 is not an XML media type',), 'encoding': u'UTF-8', 'entries': [], 'feed': {'meta': {'content': u'1;url=/login?from=%2Fview%2FTeamBuilds%2Fjob%2FTeam-SOMETEAM-CI%2FrssAll%3Fflavor%3Drss20', 'http-equiv': u'refresh'}, 'summary': u'Authentication required'}, 'headers': {'connection': 'Close', 'content-length': '653', 'content-type': 'text/html;charset=UTF-8', 'date': 'Wed, 13 Feb 2013 16:41:43 GMT', 'server': 'Winstone Servlet Engine v0.9.10', 'set-cookie': 'JSESSIONID.61010deb=0dfed6g10dd99a7ef66936b35bf3ad7d; Path=/; Secure; HttpOnly', 'x-powered-by': 'Servlet/2.5 (Winstone/0.9.10)'}, 'href': u'https://jenkins01.MYDOMAIN.com:8443/view/TeamBuilds/job/Team-SOMETEAM-CI/rssAll?flavor=rss20', 'namespaces': {}, 'status': 403, 'version': u''}
I have done. Some of feed engines don't accept custom user-agent. change user-agent to browser's user-agent(chrome or firefox).
@developer0725 thanks for having it resolved. It has been over 5 years since this bug was opened. I have moved on but nevertheless, I hope it helps those who stumble across this problem. Much appreciated. 👍