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: Daniel Stenberg via curl-users <curl-users_at_lists.haxx.se>
Date: Fri, 15 Apr 2022 23:11:06 +0200 (CEST)
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.
Date: Fri, 15 Apr 2022 23:11:06 +0200 (CEST)
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.
-- / daniel.haxx.se | Commercial curl support up to 24x7 is available! | Private help, bug fixes, support, ports, new features | https://curl.se/support.html -- Unsubscribe: https://lists.haxx.se/listinfo/curl-users Etiquette: https://curl.haxx.se/mail/etiquette.htmlReceived on 2022-04-15