Need resume support for really nasty proxies (or a way to extend cache manually)
rassie opened this issue · 2 comments
In my environment, the proxy is really nasty, it interrupts the download at some undefined point to check it for viruses. npm_lazy needs a way to either resume a download (which works with this proxy) or provide a way to add a tarball to the cache manually (i.e. download first and then add).
Hmm. Does the proxy also MITM https connections? If not maybe that could stop it from interrupting downloads.
Alternatively, if there is a node module that does proxying that you know works even in your environment, let me know (preferably with a usage example) and I'll take a look at using it.
A third solution for now using file copying / extending the cache manually: run npm_lazy on a different server outside the proxy, make some requests against it and then copy the cache folder to the other machine. The cache folders should be fully portable as long as the npm_lazy version matches though I've never tried it myself.
closing to clean up the issues list a bit