Macnetworkprog

Download

macnetworkprog@lists.apple.com

October 2017

4 participants
12 discussions

Re: Why does NSURLSession return NSURLResponse instead of NSHTTPURLResponse
by Jens Alfke 17 Oct '17

17 Oct '17

site_archiver(a)lists.apple.com Delivered-To: macnetworkprog(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=oSufXCTCWPxmeD/Lsuc6cntsPWF0r NXAVab65TGN6Zw=; b=evO6UDelo//3R/D8gWWDrbJIWZyTjXgxCzEbKz9RB1JZa NBZb5PatjEt/jgYe6vDn1WQQKwHIWXx2zv82HUB+BsALs+Cs9SjKCmR5ZwOqdmLi VXMdVmNjy99ucoQ0pVKrs9TfnZuv9QM+OjyHY8rVl1q1xaPoKivp9NoYN3MFRTY5 TNH/IIKadboV8EZhymFZgOeMtF2Dhca9UEDzl7+EsC5hHrmlmVd6pFzr39gBsqKl 3j2BcDGRXx/CZYByjUGw5eCV2p89NCZG+jyij0/KLnvPw1BJm8A06tygeTzrMHCJ xI+Lw0xce3LBvMNZpXRZGBhuNgRezyaSHardHsSWw== > On Oct 17, 2017, at 3:05 PM, Sebastien Boisvert <sebastienboisvert(a)yahoo.com> > wrote: > > I've noticed that most times, the response will come back as a > NSHTTPURLResponse, other times only as a NSURLResponse (which leads to a > crash when I try to get the -statusCode). I’ve never seen a request for an HTTP[S] URL return a response that wasn’t an NSHTTPURLResponse, so that’s definitely unexpected! Are you certain that the URLs in your requests always have the scheme “http” or “https”? —Jens _______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list (Macnetworkprog(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/macnetworkprog/site_archiver%40list… This email sent to site_archiver(a)lists.apple.com

1 0

Why does NSURLSession return NSURLResponse instead of NSHTTPURLResponse
by Sebastien Boisvert 17 Oct '17

17 Oct '17

site_archiver(a)lists.apple.com Delivered-To: macnetworkprog(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1508277978; bh=04HcwUlFce8t4UskzmQRWIi+cSruI7pDD8AenVRDlIY=; h=Date:From:Reply-To:To:Subject:References:From:Subject; b=nvuoQlObn/qGHfqA5hEKCGVlbw1F9M+OxCcx3iHLhOPPMHMmi+b3hZ/f3htrwz31ECjL1QBdCAiVqX4lCovtS4tsWakRRunfFhN0TXA5oI+IxSiR4NvUAOht6UjXRtlNzamtayCt9UxHT8ScIeL9R9Q5df1qJRHOHk9kVFymT2hmqzWf8pAO+CDaGqAWqJWe4yGaEhoTYArzKgXqNVrImDvujax0Tbt0vxx6PqztuqiE2hYf/La3f3cmBP5YVg4wtlEc6k4gYU3E8AQb10OtH0CHZHU5GiHKSeGuNVx0ajVmMCj75B89YZ1SdsyHKDluY9KFgs0h5PW9819y2OzkcA== I have the following (simplified) code snippet: [myURLSession dataTaskWithRequest:request completionHandler:^(NSData * _Nullable data, NSURLResponse * _Nullable response, NSError * _Nullable error) { NSHTTPURLResponse* httpResponse = (NSHTTPURLResponse*)response; NSUInteger responseCode = httpResponse.statusCode; (do something based on responseCode value) .... }] resume]; 'request' is a NSURLRequest to an HTTPS server. I've noticed that most times, the response will come back as a NSHTTPURLResponse, other times only as a NSURLResponse (which leads to a crash when I try to get the -statusCode). I haven't been able to determine why/when NSURLSession will return a NSHTTPURLResponse vs a NSURLResponse (the requests always go to a HTTP server, with a http(s):// scheme). I would expect that since the request is sent to a HTTP server/scheme, it would always return a NSHTTPURLResponse object. What would make it a NSURLResponse (when a valid response is returned) instead of a NSHTTPURLResponse? _______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list (Macnetworkprog(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/macnetworkprog/site_archiver%40list… This email sent to site_archiver(a)lists.apple.com

1 0