This looks like standard authentication method. Just the final POST is different as it would open a new connection from the server to your App in which case your app is the HTTP server and "Server" is the http client. This wont work over network translation (NAT) and looks very odd. Normally the 200 OK return message would deliver the content to you.
Are you really sure that's the way it is supposed to be?
I have a small library doing the HTTP server part if you need it, contact me offline but I guess your setup is rather unusual if its really is what you describe here.
Hi Jens,
Thanks for your info.
Currently, I’m working on an application which needs to act as server and client role in the same time; The traffic flow like:
MyApp Server
——- GET——----------->
<——Challenge ——-----
——— GET/with auth—>
<—— 200 OK ————
<—— POST —————
…
This is the reason that I can not use NSURLConnection, can I?
The strange thing to me is the NSURLConnection can work for the same server.
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