Databases
StackOverflow2013
Postsdbo
POHow do I enable https support in libcurl?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow do I enable https support in libcurl?
    primarykey
    data
    text
    <p>When I try to <code>$ brew update</code> I'm getting the error:</p> <pre><code>error: Protocol https not supported or disabled in libcurl while accessing https://github.com/mxcl/homebrew/info/refs?service=git-upload-pack </code></pre> <p>However, when I <code>$ curl --version</code>, I see:</p> <pre><code>curl 7.21.4 (x86_64-apple-darwin12.2.0) libcurl/7.21.4 OpenSSL/0.9.8y zlib/1.2.5 libidn/1.20 Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtsp smtp smtps telnet tftp Features: IDN IPv6 Largefile NTLM SSL libz </code></pre> <p>Unless I'm missing something, that looks good to me. Notice that <code>https</code> is listed in the protocols list.</p> <p><code>$ which curl</code> yields a suspicious response:</p> <pre><code>/usr/local/php5/bin/curl </code></pre> <p>Hmmmmm...maybe <code>brew</code> is using a different <code>curl</code> (like the one at <code>/usr/bin/curl</code>). Let's see:</p> <p><code>$ /usr/bin/curl --version</code></p> <pre><code>curl 7.24.0 (x86_64-apple-darwin12.0) libcurl/7.24.0 OpenSSL/0.9.8y zlib/1.2.5 Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtsp smtp smtps telnet tftp Features: AsynchDNS GSS-Negotiate IPv6 Largefile NTLM NTLM_WB SSL libz </code></pre> <p>Okay, it's obviously a different install of <code>curl</code>, but it's also listing <code>https</code> in the protocols list, and has the OpenSSL info there too.</p> <p>BTW: I get the same error if I try to use an <code>https</code> URL with any <code>git</code> repo on my machine.</p> <p>Questions:</p> <ol> <li><del>How can I determine the path to the <code>curl</code> that <code>brew</code> is using?</del></li> <li>How do I enable support for <code>https</code> in <code>libcurl</code>?</li> </ol> <p><strong>UPDATE:</strong> I was able to determine the path to <code>libcurl.4.dylib</code> that <code>git</code> (and <code>brew</code>) are using by following deltheil's method below. The path is:</p> <pre><code>/usr/lib/libcurl.4.dylib (compatibility version 6.0.0, current version 6.1.0) </code></pre> <p>So I tried this:</p> <pre><code>$ brew install curl --with-libssh2 </code></pre> <p>Luckily curl is available at a non-SSL URI, so it actually did insstall. It didn't symlink into <code>/usr/local</code>, but that's fine with me (I think). So I did this:</p> <pre><code>$ cd /usr/lib $ mv libcurl.4.dylib libcurl.4.dylib.bk $ ln -s /usr/local/Cellar/curl/7.30.0/lib/libcurl.4.dylib libcurl.4.dylib $ brew update </code></pre> <p>But it's still throwing me this error:</p> <pre><code>error: Protocol https not supported or disabled in libcurl while accessing https://github.com/mxcl/homebrew/info/refs?service=git-upload-pack </code></pre> <p>So now the question exclusively becomes: How do I enable support for <code>https</code> in <code>libcurl</code>?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USBen Harold
    1. USBen Harold
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload