NSURLConnection "just works". Authentication not challenged.
NSURLConnection "just works". Authentication not challenged.
- Subject: NSURLConnection "just works". Authentication not challenged.
- From: Jerry Krinock <email@hidden>
- Date: Fri, 9 Nov 2007 22:54:32 -0800
Even though I'm now using NSURLCredentialPersistenceNone, I still find
that after sending a certain message to a certain secure server,
further requests no longer elicit authentication challenges until my
app quits. Thus, I cannot change user accounts, by sending a
different credential.
Either NSURLConnection is re-using a previous credential, or the host
is not requiring it. The server always works as expected when I use
curl with different -uAccount:Password arguments. This implies that
NSURLConnection is guilty. But the trouble repeatably starts when I
send a certain application-layer message to the server, which implies
that the server is guilty.
Since NSURLConnection and even curl keep all this under the hood, and
since this server requires SSL which encrypts most of the action, I'm
having difficulty determining which is guilty. Can anyone suggest how
to troubleshoot such a thing?
Thanks,
Jerry Krinock
P.S. If anyone wants to play with a demo app...
http://sheepsystems.com/engineering/NSURLCrosstalk.zip
It's a little Cocoa app but the GUI is not being used right now. The
test commences when -applicationDidFinishLaunching: and takes about 10
seconds to run, printing results to the console. Note that the three
requests in "Section A" report authentication challenges being
received, but after sending the "update" message, the three identical
requests in "Section B" do not get authentication challenges.
_______________________________________________
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