Re: NSURLSessionStreamTask and HTTP(S) proxies
Re: NSURLSessionStreamTask and HTTP(S) proxies
- Subject: Re: NSURLSessionStreamTask and HTTP(S) proxies
- From: Daryle Walker <email@hidden>
- Date: Tue, 07 Feb 2017 15:15:30 -0500
> On Feb 7, 2017, at 3:57 AM, Quinn The Eskimo! <email@hidden> wrote:
>
>
> On 6 Feb 2017, at 10:33, Thibault Martin-Lagardette <email@hidden> wrote:
>
>> I find this highly surprising, as it is absolutely possible to use an HTTP(S) proxy for raw TCP/IP connections, simply by using the HTTP CONNECT method (RFC 2817 <https://tools.ietf.org/html/rfc2817>)
>
> Indeed. And NSURLSession will do this for HTTPS requests. I suspect that the fact that it doesn’t do this for stream tasks is more an accident of history than anything else (NSURLSession was originally designed as an HTTP[S] API, and for HTTP it can just use the HTTP proxy in the standard way).
[Sorry for the potential thread hijack.]
Not too surprising, since the point of the stream tasks seems to be going below the HTTP/FTP/SMTP/IMAP/NNTP/Gopher/etc level. One use is to implement said protocols. That’s why I’ve been asking for an example of how to use stream tasks; we have no guide. (I haven’t seen any by Apple or on GitHub so far. There’s a bug report project on GitHub, as I said in another post, but that person doesn’t actually use the class. Correct me if there is a proper example out there.)
—
Daryle Walker
Mac, Internet, and Video Game Junkie
darylew AT mac DOT com
_______________________________________________
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