On 06 Jul 2015, at 01:36, Jens Alfke <jens@mooseyard.com> wrote:

...

On Jul 5, 2015, at 3:21 PM, Antonio Nunes <devlists@sintraworks.com> wrote:

As you can see, the content body is not there.

Yes, but since the server abruptly closed the socket, it might be that the NSURLSession didn’t get a chance to send the body. The fact that it included a Content-Length: 122 header tells me that it _intended_ to send the body — if it had decided that “I never send a body in a GET”, it would have left the Content-Length at zero.

My guess is that some innocuous difference in the request triggered a bug on the server side and caused the servlet or PHP script or whatever to throw an exception. It’s definitely not a valid response for the server to close the socket like that — in my experience it only happens if there’s a serious unhandled error on the server. Frankly, this seems a likely explanation, assuming that the server developers’ coding skills are on par with their API design skills.

Haha. You know, I haven’t worked enough with them to be able to gauge that. ;-) Anyway, you’re probably right, and I just received a message that they will make the call available through a POST request, so let’s hope that will serve to work around the issue. Thanks for all your help. -António _______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list (Macnetworkprog@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/macnetworkprog/site_archiver%40lists... This email sent to site_archiver@lists.apple.com