HTTP Digest Authentication: providing wrong username&pw => endless loop op:connection:willSendRequestForAuthenticationChallenge about mknetworkkit HOT 2 CLOSED

If you add

if (challenge.previousFailureCount  > 0) {
    [challenge.sender cancelAuthenticationChallenge:challenge];
    return;
}

to the top of connection:willSendRequestForAuthenticationChallenge: it works just fine. Instead of a loop you will get an NRURLDomain error NSURLErrorUserCancelledAuthentication if you provide wrong credential... time for me to fork it ;-)

Cheers,
Thomas

from mknetworkkit.

Another observation: if you provide wrong credentials from the very beginning, MKNetworkOperation fails with error 401 (which is fine). if you start with proper credentials a change them later on, you'll get the loop described above. "Later on" means: stop MKNetwork-iOS-Demo in iOS Simulator, change credentials in AuthTestEngine.m and compile&start the App via Xcode again - there seems to be some caching of the credentials. Please note, that http://api.mk.sg/mknetworkkit/digest_auth.php is not suitable for testing, since it always seem to respond with http status 200.

Update: this observation seems to be related to my comment on issue #35, double caching

Cheers,
Thomas

from mknetworkkit.