NSURLConnection Authentication Challenges: Tiger bad, Leopard worse.
NSURLConnection Authentication Challenges: Tiger bad, Leopard worse.
- Subject: NSURLConnection Authentication Challenges: Tiger bad, Leopard worse.
- From: Jerry Krinock <email@hidden>
- Date: Thu, 1 Nov 2007 21:06:42 -0700
Running Under Tiger:
When I would connect to an online service such as del.icio.us which
requires authentication, instead of presenting me with the
authentication challenge, NSURLConnection would use the default
credential from Keychain. This is confusing if the user has more than
one del.icio.us account. But I was able to work around this by,
before each connection, creating a credential for the desired account
and setting it to be the default credential for del.icio.us' host/
realm protection space. [1]
Running Under Leopard:
Using the same build under Leopard, the behavior is first better, but
then worse. Instead of using credential storage, it now gives me an
authentication challenge during the first connection, so I supply it
with a credential for the desired account. However, for subsequent
connections in the remainder of the session, I don't get any more
authentication challenges; it just keeps using this same credential.
Problem: This makes it impossible to access data from a different
del.icio.us account without a relaunch.
Can anyone give me some more insight into this that suggest a
workaround? I've read through the stuff about NSURLConnection in
Leopard's Foundation release notes but don't see any changes regarding
authentication challenges.
Thanks,
Jerry Krinock
[1] Thanks to Buzz Andersen posting his Cocoalicious project code.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden