0
@@ -181,6 +181,27 @@ You can then call to_xml and rAtom will serialize the extension elements into xm
0
Notice that the output repeats the xmlns attribute for each of the extensions, this is semantically the same the input XML, just a bit
0
ugly. It seems to be a limitation of the libxml-Ruby API. But if anyone knows a work around I'd gladly accept a patch (or even advice).
0
+=== Basic Authentication
0
+All methods that involve HTTP requests now support HTTP Basic Authentication. Authentication credentials are passed
0
+as :user and :pass parameters to the methods that invoke the request. For example you can load a feed with HTTP Basic Authentication using:
0
+ Atom::Feed.load_entry(URI.parse("http://example.org/feed.atom"), :user => 'username', :pass => 'password')
0
+Likewise all the Atom Pub methods support similar parameters, for example you can publish an Entry to a Feed with authentication
0
+ feed.publish(entry, :user => 'username', :pass => 'password')
0
+Or destroy an entry with:
0
+ entry.destroy!(:user => 'username', :pass => 'password')
0
+rAtom doesn't store these credentials anywhere within the object model so you will need to pass them as arguments to every
0
+method call that requires them. This might be a bit of a pain but it does make things simpler and it means that I'm not responsible
0
+for protecting your credentials, although if you are using HTTP Basic Authentication there is a good chance your credentials aren't
0
+very well protected anyway.
0
* Support partial content responses from the server.
0
@@ -189,7 +210,6 @@ ugly. It seems to be a limitation of the libxml-Ruby API. But if anyone knows a
0
* All my tests have been against internal systems, I'd really like feedback from those who have tried rAtom using existing blog software that supports APP.
0
* Handle all base uri tests.
0
-* Handle HTTP basic authentication.
Comments
No one has commented yet.