This forum has been archived. All content is frozen. Please use KDE Discuss instead.

syndication broken in 4.3.1?

Tags: None
(comma "," separated)
rtweed
Registered Member
Posts
2
Karma
0

syndication broken in 4.3.1?

Fri May 03, 2013 11:56 pm
Running Fedora 17, upgraded from 4.3.0 to 4.3.1. Was trying to get past the 'could not find a valid link to torrent' error in 4.3.0 syndication, and noticed a few code checkins on the syndication plugin so I thought I'd give it a try.

I'm using both thebox.bz and eztv's RSS feeds. eztv has always worked 100%, thebox is flaky at best.

Neither work under 4.3.1. The eztv feed gives a 'Failed to load feed http://www.ezrss.it/feed/: File not found' error, and the thebox feed gives a 'Failed to load feed : Unknown retriever error'. Again, both feeds were working before the 4.3.1 update and no other configuration has been changed.. and both feeds are currently fine if I access them directly.
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS

Re: syndication broken in 4.3.1?

Sun May 05, 2013 6:32 am
Does the command "kioclient cat <url>" work for these URLs?
If it does not, it indicates the problem may be in KIO's HTTP support.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
rtweed
Registered Member
Posts
2
Karma
0

Re: syndication broken in 4.3.1?

Tue May 14, 2013 12:38 am
bcooksley wrote:Does the command "kioclient cat <url>" work for these URLs?
If it does not, it indicates the problem may be in KIO's HTTP support.


No - 'kioclient cat <url>' returns a 404. This suggests to me that the auth information isn't being passed correctly. If I use the same url in a browser that's logged in, I get a valid .torrent - but without logging in, I get the same 404 that kioclient returns.

I've tried specifying the auth cookie using the 'cookies' option and as part of the RSS feed configuration with the same results.
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS

Re: syndication broken in 4.3.1?

Thu May 16, 2013 5:37 am
If you use those same URLs in a browser which is not logged in - do they work?
If they do not, then this very likely explains why it fails. If it does - then it indicates a bug in KDE somewhere.

As a workaround - try logging in using Rekonq or Konqueror, which both use KIO as well, and which should therefore allow KTorrent to work as well.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]


Bookmarks



Who is online

Registered users: Bing [Bot], Evergrowing, Google [Bot], rblackwell