Delicious API and urllib2

[Bill]

The delicious api requires http authorization (actually https). A
generic delicious api post url is "https://
username[email protected]/v1/posts/add?url=http://
example.com/&description=interesting&tags=whatever".

This works fine when entered in the Firefox address bar. However
urllib2.urlopen(delicious_post_url) chokes and returns
"httplib.InvalidURL: nonnumeric port: '(e-mail address removed)".

Delicious really wants that authorization stuff embedded in the url as
it also rejected my attempts at using urllib2.HTTPBasicAuthHandler(),
etc.
Anybody have any hints?

 

[Brent Bloxam]

The delicious api requires http authorization (actually https). A
generic delicious api post url is "https://
username[email protected]/v1/posts/add?url=http://
example.com/&description=interesting&tags=whatever".

This works fine when entered in the Firefox address bar. However
urllib2.urlopen(delicious_post_url) chokes and returns
"httplib.InvalidURL: nonnumeric port: '(e-mail address removed)".

Delicious really wants that authorization stuff embedded in the url as
it also rejected my attempts at using urllib2.HTTPBasicAuthHandler(),
etc.
Anybody have any hints?

What failure were you experiencing when you were using the
HTTPBasicAuthHandler?

Did you follow the sample code from the docs?

 

[Max Erickson]

The delicious api requires http authorization (actually https). A
generic delicious api post url is "https://
username[email protected]/v1/posts/add?url=http://
example.com/&description=interesting&tags=whatever".

The simplest way is probably to manually add the authentication
header, as shown here:

http://code.activestate.com/recipes/267197/#c2

This article discusses the above strategy, and a strategy using
HTTPBasicAuthHandler with a password manager default realm (I think
getting the realm correct is what has stymied me in my attempts to use
handlers, rather than injecting the header):

http://www.voidspace.org.uk/python/articles/authentication.shtml


Max