Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
Re: Supporting socks proxy via unix sockets
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Alex Bligh via curl-users <curl-users_at_lists.haxx.se>
Date: Sat, 16 Apr 2022 16:18:42 +0200
> On 15 Apr 2022, at 23:11, Daniel Stenberg <daniel_at_haxx.se> wrote:
>
> On Fri, 15 Apr 2022, Alex Bligh wrote:
>
>>> Like this:
>>>
>>> socks5h://localhost/path/to/socks.sock
>>
>> For socks5h maybe, but if you want sockets to work in general in URLs, that's not going to work. Consider making an http request:
>>
>> http://localhost/path/to/socks.sock
>>
>> is a perfectly valid 127.0.0.1:80 URL. But using the above scheme it could be a socket URL.
>
> I spoke about the URL format used to specify *proxies*, like the argument set with -x. That's not the URL used for transfers, so there's no way a "real" URL can be mistaken for a proxy or vice versa.
Yes. I was suggesting it might be useful to have a URL format that worked everywhere, not just for proxies. For example SMTP (in the form of LMTP) is I believe often accessed via a socket (though that admittedly doesn't require a path in the URL either).
Date: Sat, 16 Apr 2022 16:18:42 +0200
> On 15 Apr 2022, at 23:11, Daniel Stenberg <daniel_at_haxx.se> wrote:
>
> On Fri, 15 Apr 2022, Alex Bligh wrote:
>
>>> Like this:
>>>
>>> socks5h://localhost/path/to/socks.sock
>>
>> For socks5h maybe, but if you want sockets to work in general in URLs, that's not going to work. Consider making an http request:
>>
>> http://localhost/path/to/socks.sock
>>
>> is a perfectly valid 127.0.0.1:80 URL. But using the above scheme it could be a socket URL.
>
> I spoke about the URL format used to specify *proxies*, like the argument set with -x. That's not the URL used for transfers, so there's no way a "real" URL can be mistaken for a proxy or vice versa.
Yes. I was suggesting it might be useful to have a URL format that worked everywhere, not just for proxies. For example SMTP (in the form of LMTP) is I believe often accessed via a socket (though that admittedly doesn't require a path in the URL either).
-- Alex Bligh -- Unsubscribe: https://lists.haxx.se/listinfo/curl-users Etiquette: https://curl.haxx.se/mail/etiquette.htmlReceived on 2022-04-16