The client doesn't recognize HTTP auth challenges, i.e. a 401 response status. Instead the connection just fails (with no indication why, because the API doesn't expose what the HTTP status was.)
There would need to be new API to support this. At the very least allowing the caller to register a username and password for Basic auth, but it'd be better to have a delegate-based auth-challenge callback similar to the one NSURLConnection uses.
The client doesn't recognize HTTP auth challenges, i.e. a 401 response status. Instead the connection just fails (with no indication why, because the API doesn't expose what the HTTP status was.)
There would need to be new API to support this. At the very least allowing the caller to register a username and password for Basic auth, but it'd be better to have a delegate-based auth-challenge callback similar to the one NSURLConnection uses.