本文介绍了Perl Windows CPANM代理问题的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

解决了一些问题之后,我通过 perl -MCPAN -e shell 在具有DwimPerl的Work Windows 7机器上成功使用CPAN conf init / proxy /

After solving a few issues, I've Succeeded with CPAN on my Work Windows 7 Machine with DwimPerl via perl -MCPAN -e shell and o conf init /proxy/

ftp:
http: http://192.168.1.1:8080
no:
Username: Chris@work
Password: SuperDeDuperSecretPassword

CPAN有效。我能够安装/构建。

CPAN works. I'm able to install/build.

似乎无论我做什么,CPANM都不想越过代理:

It seems that no matter what I do, CPANM doesn't want to get past the proxy:

C:\>cpanm WWW::Mechanize
! Finding WWW::Mechanize on cpanmetadb failed.
501 protocol scheme 'wwwproxy.work.com' is not supported
C:\> cpan WWW::Mechanize
...
...
...
c:\Programs\Dwimperl\c\bin\dmake.exe INSTALL -- OK

两者之间有什么不同?什么会导致CPAN成功而CPANM却因501而失败?

What's different between the two and what would cause CPAN to succeed while CPANM fails with a 501?

推荐答案

发布此帖子10分钟后,我与同事进行了简短的交谈。他提到了环境变量。我验证了我之前确实已经添加了Windows Environment变量。对他们的快速更新:

10 minutes after I posted this, I had a brief conversation with a coworker. He mentioned environment variables. I verified that I had indeed added Windows Environment variables previously. A quick update to them:

User Variables for Chris:
HTTP_Proxy:  http://192.168.1.1:8080
HTTP_proxy_pass: SuperDeDuperSecretPassword
HTTP_proxy_user: Chris@Work

我从 wwwproxy.work.org http://192.168.1.1:80 (CPAN抱怨没有HTTP,所以我认为它也需要完整的URL)。

I changed it from wwwproxy.work.org to http://192.168.1.1:80 (CPAN complained without the HTTP, so I think it needed the full URL as well).

并且我的名字有错字:(

AND I had a typo in my name :(

CPANM现在可以使用。

CPANM works now.

这篇关于Perl Windows CPANM代理问题的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

10-18 14:09