Re: [syndication] Authenticated Access to RSS

[burton@openprivacy.org]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Julian Bond <julian_bond@voidstar.com> writes:

> In article <167171663128.20011215211355@loy-fu.com>, Dion Loy <dion-
> yhoo@loy-fu.com> writes
> >This doesn't and shouldn't require RSS-level support in the RSS spec.
> >This is already done at the HTTP level. It would be relatively
> >trivial for current RSS readers (if they don't already) to support
> >HTTP authentication (base64 at the very least, maybe NTLM if they want
> >to get fancy).
> 
> The key here is the words "if they don't already". And the answer is "they
> don't". Generally the libraries people are using, curl, Indy, php, perl, could
> support normal http authentication, or even something built on SSL. Or the
> same cookie based authentication used for session management in the main site.
> 
> But I'm pretty sure nobody does.

If these libraries do not support transparent auth, redirect and SSL, they are
broken.

The java.net implementation supports HTTP, SSL and auto right now.

Give Reptile SSL or URLs that require authentication and it will work :)

Kevin

- -- 
Kevin A. Burton ( burton@apache.org, burton@openprivacy.org, burtonator@acm.org )
             Location - San Francisco, CA, Cell - 415.595.9965
        Jabber - burtonator@jabber.org,  Web - http://relativity.yi.org/

Criticizing an Open Source project for their level of progress is akin to
criticizing someone else for not giving enough to charity, while giving none
yourself.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Get my public key at: http://relativity.yi.org/pgpkey.txt

iD8DBQE8H+RyAwM6xb2dfE0RAtASAJ9bDJ+1UWse1GplKwQkTF3wabWYoACeNHpr
A/g4CQGEyt+ByzbYAjj3k3I=
=VgCu
-----END PGP SIGNATURE-----