-
Notifications
You must be signed in to change notification settings - Fork 32
qiime-deploy behind proxy #57
Comments
Short follow up:
|
In the past when I have encountered this problem, I will download the |
Here is the nasty hack to use wget instead (though this might not be that helpful for mac users)
I am not confident enough in python but might it be possible to use urllib2 or the requests package? Best, |
I found out that it works when using the plain FancyURLopener class. I provided a fix, see my pull request. Best, |
It seems that my fix did not solve the problem, sorry. Maybe a solution using urllib2 or the requests package works better. Peter |
Ok, I did some more investigation. Downloading with urllib tries to send the following:
The proxy answers:
Downloading with wget, however sends:
thus establishing a proper https connection:
I found a solution involving urllib2 that seems to work better. After testing I will generate a pull request with the fix. Best, |
…sible Replaced the urllib method of downloading files by code that uses urllib2. It seems that urllib is not able to download files from https urls. See here qiime#57
…sible Replaced the urllib method of downloading files by code that uses urllib2. It seems that urllib is not able to download files from https urls. See here qiime#57
In my work environment I have to use a proxy. This causes some problems downloading software with qiime-deploy.
The environment variables ($http_proxy, $https_proxy, $ftp_proxy,. $all_proxy) are all set appropriately but the download_file() function in lib/util.py fails for some downloads. The following tools are not deployed:
drisee, ea-utils, tornado, pyzmq, setuptools, MySQL-python, pyqi, sphinx, biom-format, emperor, pynast, tax2tree, qiime, qiime-galaxy, galaxy
(It might have something to do with the https:// links?!)
I could replace the Python urllib downloading with a nasty hack to use wget instead but maybe one of you could investigate this and probably fix this.
Another thing: Behind the proxy, I have problems to access git://github... urls. This can be circumvented by using https://github... instead.
Quite automatically this will be done with the following git config:
However, it would be easier for people if you would put the https urls of github directly in the accroding qiime-deploy-conf files.
Best,
Peter
The text was updated successfully, but these errors were encountered: