Re: NSURLConnection callbacks in the presence of errors
Re: NSURLConnection callbacks in the presence of errors
- Subject: Re: NSURLConnection callbacks in the presence of errors
- From: Jens Alfke <email@hidden>
- Date: Mon, 13 Jan 2014 09:43:26 -0800
On Jan 13, 2014, at 2:19 AM, Quinn The Eskimo! < email@hidden> wrote: Right. The underlying cause of this delay is NSURL{Session,Connection}'s content type sniffing: to handle certain edge cases NSURL{Session,Connection} must wait for a certain amount of data to arrive so that it can feed that data into the content type sniffing code. There should be an option to disable that feature and we're using <rdar://problem/8971926> to track that requirement.
OK, thanks for the info. Until then, is there any workaround on the server side? E.g. can I set any HTTP response headers that will make the framework decide that it doesn’t need to do the content type sniffing?
—Jens |
_______________________________________________
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