When an HTTP request includes
Expect: 100-continue
a special protocol is included in the header. It is difficult but useful.
In the experiments we performed, iOS 8 version NSURLSessiondoes not seem to send this default message waiting header. We are still exploring whether it works explicitly.
The only link we can find in the Apple documentation claims 100-continueto work for the predecessor NSURLSession, which is equal NSURLConnection. It says
If you upload data to a compatible server, the URL loading system also supports the HTTP status code 100 (Continue), which allows you to continue downloading where it was stopped in case of an authentication error or other failure. To enable continued download support, set the Expect: header on the request object to 100-continue.
What do I need with
In order of preference:
- Details on how it works from Apple.
- Any information on how this works on iOS from anyone.
I am definitely interested to know how this works on OS X.
† I’m not sure that even a good description of what should happen with the 100-sequel, because IIUC is that the request body is large, and you better send the request header, get it by a pre-approved server, and then start sending the body.
application
- , , 100-continue.
- , github, NSURLConnection OS X.