-
Notifications
You must be signed in to change notification settings - Fork 66
elm-package does not support proxy #113
Comments
Here's the exact error message I get:
Would also like to point out that I get the same error message when I'm trying to run |
Addresses proxy issue reported in #113
Thanks for the very informative issue! I have bumped the constraint on http-client so that anyone building from source will get the fixed version. This means that the fix will definitely be in the next release! Are you able to build from source in the meantime? |
Thanks! I got the binaries from npm (which also didn't easily support proxy, the binaries had to be downloaded separately in order to complete the installation script). Hopefully they get updated in the next release. |
Hi, I'm trying Elm and I already love this small, wonderful language. I have just the exact issue that is described here
I'm on Windows using MinGW and I'm behind a proxy. Normally my proxy configuration works perfectly with other command-line applications like git. Just a precision, in the username I have a space and in the password some special characters url-encoded like %3a%2a. May be these special characters trigger in some way the error ? Right now this is not a big problem for me because I can compile stuff at home, on linux, but it is a little bit imitating if I want to test or develop something at work. Any solution or workaround ? EDIT: I did find myself the solution, I needed to replace the space in the username with %20, the url-encoded escape sequence. |
I'm having the same |
I'm having an issue as well on Windows 7
What (environment) variable do I need to set exactly? |
set http_proxy = http://id:pwd@proxyip:port |
Thanks! In PowerShell it was $env:http_proxy = "myproxy.com:8080"
$env:https_proxy = "myproxy.com:8080" |
When trying to install a package with elm-package, I get an InvalidProxyEnvironmentVariable-exception.
It seems to be a problem with the http library used as described in this StackOverflow post:
http://stackoverflow.com/questions/31138915/haskell-network-http-conduit-exception-invalidproxyenvironmentvariable-http-pr
According to the post, a fix has been made already and might event have been pushed upstream already.
The text was updated successfully, but these errors were encountered: