Page 1 of 1

Cookies for getting feeds

Posted: 27 Apr 2010, 21:48
by jsdm
I have a RSS feed that's for a members-only organization. If I access the feed without having an authentication cookie, it redirects to a webpage that asks me to log in. Of course, tt-rss can't parse that webpage as RSS XML so it gets an error. I tried typing the username/password in the prefs for the feed but that doesn't seem to work. It really requires a cookie.

Is there any way to give a cookie to the update daemon for it to use when updating the feed?


Re: Cookies for getting feeds

Posted: 30 Apr 2010, 22:36
by MattKatz
That one is tougher than it sounds.
Authenticated RSS feeds are rough, but forms based authenticated feeds are completely goofy.

This would meant that TT would have to parse the login form, fill in the user/pass, get the cookie, then request the rss...

Re: Cookies for getting feeds

Posted: 02 May 2010, 00:05
by jsdm
That would obviously be ridiculous but I think there's an easier way. I can log in with my browser and export the cookie. I've already done this so I know the cookie name and value that needs to be presented by tt-rss to the server. I just need a way to tell tt-rss about the cookie and have it send it with the request.

Something like "wget --load-cookies" would be fine.

Re: Cookies for getting feeds

Posted: 03 May 2010, 12:01
by Joschasa
Had the same problem with the dokuwiki "recent changes" feed.
This feed was protected and only had items while logged in.
I found out, that the feed.php accepted the parameters u and p (username/password), so i could "login" without httpauth, cookies, ...

Perhaps your application supports this as well?

Re: Cookies for getting feeds

Posted: 03 May 2010, 22:35
by jsdm
I tried entering the username and password in the tt-rss preferences but that didn't work.

The site in question is using vBulletin 3.6.8 if anybody has any tips on that. Thanks.

Re: Cookies for getting feeds

Posted: 07 May 2010, 23:16
by fox
I'm sorry, but importing cookies into tt-rss is not going to happen. This problem can be solved by proper configuration on the other end (e.g. the feed should accept HTTP Auth to show protected content, like Livejournal does).