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: Balakrishnan Balasubramanian via curl-users <curl-users_at_lists.haxx.se>
Date: Mon, 25 Apr 2022 15:36:09 -0400
This is implemented in PR. https://github.com/curl/curl/pull/8668
Please take a look.
Thanks,
Bala
On 2022-04-15 05:32, Daniel Stenberg wrote:
> On Mon, 11 Apr 2022, Dan Fandrich via curl-users wrote:
>
>> My preference is still for the file: style triple-slash syntax
>> socks5h:///path/to/socks.sock but it sounds like that won't work
>> without changes to the URL parser. Given that a normal socks path
>> will never use the path portion of the URL, it means the host part
>> could be pretty flexible. So much so that the host part could be
>> completely ignored if a path of any sort exists in the URL (I'm not
>> suggesting we do that, though).
>
> Maybe we could require "localhost" as hostname and if the URL then has
> a path it means it is a unix-socket and not a "normal one"?
>
> Like this:
>
> socks5h://localhost/path/to/socks.sock
>
Date: Mon, 25 Apr 2022 15:36:09 -0400
This is implemented in PR. https://github.com/curl/curl/pull/8668
Please take a look.
Thanks,
Bala
On 2022-04-15 05:32, Daniel Stenberg wrote:
> On Mon, 11 Apr 2022, Dan Fandrich via curl-users wrote:
>
>> My preference is still for the file: style triple-slash syntax
>> socks5h:///path/to/socks.sock but it sounds like that won't work
>> without changes to the URL parser. Given that a normal socks path
>> will never use the path portion of the URL, it means the host part
>> could be pretty flexible. So much so that the host part could be
>> completely ignored if a path of any sort exists in the URL (I'm not
>> suggesting we do that, though).
>
> Maybe we could require "localhost" as hostname and if the URL then has
> a path it means it is a unix-socket and not a "normal one"?
>
> Like this:
>
> socks5h://localhost/path/to/socks.sock
>
-- Unsubscribe: https://lists.haxx.se/listinfo/curl-users Etiquette: https://curl.haxx.se/mail/etiquette.htmlReceived on 2022-04-25