<br><br><div><span class="gmail_quote">On 5/18/06, <b class="gmail_sendername">Bčr Kessels</b> <<a href="mailto:ber@webschuur.com">ber@webschuur.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Op woensdag 17 mei 2006 19:37, schreef Dan Robinson:<br>> My reader (thunderbird) asked for authentication and everything was aok.<br><br>My reader, akregator uses the global KDE cookies. If you are logged in using<br>
the website, the feedreader gets access too. If not it will promt for<br>authentication details.<br><br>So: more advanced (better) Rss readers should/will be able to deal with<br>authentication themselves.</blockquote><div>
<br>Argh. No, incorrect. This is HTTP layer transport stuff. Different aggregators deal with it in different ways. Some just use global cookies, and don't actually handle Basic Auth at all. It works, in some cases, but is not a good solution.
<br></div><br></div>What *should* happen, is that the aggregator either:<br>* supports Basic Auth, and the user is prompted with user/pass which are then cookified/saved<br>* supports URL mangling like <a href="mailto:user:pass@feedurl.com">
user:pass@feedurl.com</a><br clear="all"><br>I haven't tested with OPML, but it should also work in conjunction with securesite and prompt. I have had some issues with NetNewsWire, which leads me to believe there are still some buglets in the securesite code (which is where the Basic Auth code is).
<br><br>-- <br>Boris Mann<br>Vancouver 778-896-2747<br>San Francisco 415-367-3595<br>Skype borismann<br><a href="http://www.bryght.com">http://www.bryght.com</a>