[MacPorts] #64744: curl: libcurl is built without the HTTPS-proxy support
MacPorts
noreply at macports.org
Fri Mar 4 15:43:42 UTC 2022
#64744: curl: libcurl is built without the HTTPS-proxy support
-------------------------+------------------------
Reporter: mouse07410 | Owner: ryandesign
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords:
Port: curl |
-------------------------+------------------------
Comment (by ryandesign):
Replying to [comment:3 mouse07410]:
> It is weird. Internally (client <-> proxy) it ''is'' HTTP...
I think you replaced the actual proxy URL in the error message with
`<host>:<port>` in this ticket's description. Did the value you replaced
start with `http://` or `https://`? Because my understanding was that you
would only see this error message if your proxy URL starts with
`https://`. But I've never tried it. If you want me to try it, let me know
how to tell curl what proxy URL to use; I've never had occasion to do so.
> I'm trying {{{+darwinssl}}} and {{{+gnutls}}}, because {{{+ssl}}} does
not seem to work.
When using `+gnutls` I still see:
{{{
Features: AsynchDNS HSTS HTTPS-proxy IDN IPv6 Largefile NTLM
NTLM_WB PSL SSL TLS-SRP UnixSockets alt-svc libz zstd
}}}
So `HTTPS-proxy` is still there.
When I use `+darwinssl` I get:
{{{
Features: AsynchDNS HSTS IDN IPv6 Largefile NTLM NTLM_WB PSL SSL
UnixSockets alt-svc libz zstd
}}}
So `HTTPS-proxy` is not present. I guess Darwin SSL mode does not support
`HTTPS-proxy` and if you want it to then you would have to get the
developer of curl to implement that.
In what way does curl with `+ssl` not work for you? That's the default
variant so surely it works for most everybody else or we'd have gotten a
zillion bug reports about it.
--
Ticket URL: <https://trac.macports.org/ticket/64744#comment:4>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list