# BinaryProvider options to curl or wget

**URL:** https://discourse.julialang.org/t/binaryprovider-options-to-curl-or-wget/23699
**Category:** Tooling
**Created:** [April 30, 2019, 2:37pm UTC](https://discourse.julialang.org/t/binaryprovider-options-to-curl-or-wget/23699 "2019-04-30T14:37:09Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![johnh](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/johnh/32/3615_2.png) [@johnh](https://discourse.julialang.org/u/johnh)
#### Post date: [April 30, 2019, 2:37pm UTC](https://discourse.julialang.org/t/binaryprovider-options-to-curl-or-wget/23699/1 "2019-04-30T14:37:09Z")

</div>

Putting my money where my mouth is I am trying to build a tarball of ffmeg on an ARM 64 system.  
BinaryProvider finds curl as its first download engine.  
As I am behind a proxy I then get  
[09:28:40] curl: (60) SSL certificate problem: self signed certificate in certificate chain  
How can I feed this option to curl: curl -k

I can define wget as the first binary provider using an ENV variable.  
But similarly how do I feed it a parameter of --no-check-certificate

---

<div class="post-metadata">

### Author: ![johnh](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/johnh/32/3615_2.png) [@johnh](https://discourse.julialang.org/u/johnh)
#### Post date: [April 30, 2019, 4:10pm UTC](https://discourse.julialang.org/t/binaryprovider-options-to-curl-or-wget/23699/2 "2019-04-30T16:10:59Z")

</div>

Answering my own question I think alias curl=“curl -k” might do the trick

---

<div class="post-metadata">

### Author: ![staticfloat](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/staticfloat/32/34_2.png) [@staticfloat](https://discourse.julialang.org/u/staticfloat)
#### Post date: [April 30, 2019, 4:34pm UTC](https://discourse.julialang.org/t/binaryprovider-options-to-curl-or-wget/23699/3 "2019-04-30T16:34:32Z")

</div>

Yeah, we don’t really support passing arbitrary parameters like that (EDIT: I should say we could, and I’m not opposed to it, but in this particular instance, I’m not sure it’s the proper fix). I consider this solution to be rather wildly insecure; have you not installed your proxy’s root certificates into your system’s certificate store?

---

<div class="post-metadata">

### Author: ![Balinus](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/balinus/32/243_2.png) [@Balinus](https://discourse.julialang.org/u/Balinus)
#### Post date: [December 9, 2019, 4:37pm UTC](https://discourse.julialang.org/t/binaryprovider-options-to-curl-or-wget/23699/4 "2019-12-09T16:37:01Z")

</div>

I also have this problem. I installed the proxy’s root certificate but seems unable to bypass some other obstacles…

Is there any way to set wget as the primary protocol/tool?

edit - I can’t download `CMake`.

edit2- Humm… I can launch th command outside Julia and then build `CMake` in Julia. Somehow, the `.curlrc` config file is not used by Julia.
