Perl LWP::UserAgent，特定 https 网站的 https 代理，未知协议错误答案

【问题标题】：Perl LWP::UserAgent, https proxy to specific https web site, unknown protocol errorPerl LWP::UserAgent，特定 https 网站的 https 代理，未知协议错误
【发布时间】：2015-01-09 00:31:25
【问题描述】：

阅读我能找到的关于主题的所有内容......无法弄清楚它是如何工作的。

我使用最新更新的（2015 年 1 月 9 日）Active State Perl 和标准方法

my $ua=LWP::UserAgent->new();  
$ua->agent('Mozilla/5.0 (Windows NT 6.1; WOW64; rv:34.0) Gecko/20100101 Firefox/33.0');
$ua->timeout(120);
$ua->cookie_jar( {} );
$ua->proxy(['https'],'https://199.200.120.140:8089') #taken from http://proxylist.hidemyass.com/search-1308872#listable
my $response = $ua->get('https://www.comparis.ch');   #this web site I struggle with, I can connect to https://github.com for example... But I also can connect to comparis.ch through same proxy using urllib3 on Python3.4...

如果有人可以解释如何从网站上获得 200？

的输出

响应返回 Timeout（如果我使用 http 代理，或者

LWP::Protocol::https::Socket: SSL connect attempt failed error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol at E:/Perl64/lib/LWP/Protocol/http.pm line 49."

如果我尝试

LWP::UserAgent->new(ssl_opts => { verify_hostname => 0, SSL_version => 'SSLv3' });

然后我得到了

LWP::Protocol::https::Socket: SSL connect attempt failed error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number at E:/Perl64/lib/LWP/Protocol/http.pm line 49.

我认为某些地区的网站连接超时，因此必须使用美国或西欧的代理。

根据要求，我添加了调试输出（对于简单的 UserAgent->new() -- 无选项），它尝试来自 http://proxylist.hidemyass.com/search-1305502#listable 的两个代理 192.3.121.204:3128 和 64.31.22.131:7808。第一个似乎只是超时（很可能被阻止），但第二个表现出不同的行为。

perl -MIO::Socket::SSL=debug4 test.pl

DEBUG: .../IO/Socket/SSL.pm:2555: new ctx 61267216
DEBUG: .../IO/Socket/SSL.pm:539: socket not yet connected
DEBUG: .../IO/Socket/SSL.pm:1769: IO::Socket::INET configuration failed
DEBUG: .../IO/Socket/SSL.pm:2588: free ctx 61267216 open=61267216
DEBUG: .../IO/Socket/SSL.pm:2593: free ctx 61267216 callback
DEBUG: .../IO/Socket/SSL.pm:2600: OK free ctx 61267216
500 Can't connect to 192.3.121.204:3128 (10060)
Content-Type: text/plain
Client-Date: Fri, 09 Jan 2015 10:15:18 GMT
Client-Warning: Internal response

Can't connect to 192.3.121.204:3128 (10060)

LWP::Protocol::https::Socket: connect: 10060 at E:/Perl64/lib/LWP/Protocol/http.pm line 49.

DEBUG: .../IO/Socket/SSL.pm:2555: new ctx 61267216
DEBUG: .../IO/Socket/SSL.pm:539: socket not yet connected
DEBUG: .../IO/Socket/SSL.pm:541: socket connected
DEBUG: .../IO/Socket/SSL.pm:563: ssl handshake not started
DEBUG: .../IO/Socket/SSL.pm:599: not using SNI because hostname is unknown
DEBUG: .../IO/Socket/SSL.pm:650: set socket to non-blocking to enforce timeout=120
DEBUG: .../IO/Socket/SSL.pm:663: Net::SSLeay::connect -> -1
DEBUG: .../IO/Socket/SSL.pm:673: ssl handshake in progress
DEBUG: .../IO/Socket/SSL.pm:683: waiting for fd to become ready: SSL wants a read first
DEBUG: .../IO/Socket/SSL.pm:703: socket ready, retrying connect
DEBUG: .../IO/Socket/SSL.pm:663: Net::SSLeay::connect -> -1
DEBUG: .../IO/Socket/SSL.pm:1780: SSL connect attempt failed

DEBUG: .../IO/Socket/SSL.pm:1785: SSL connect attempt failed error:140770FC:SSL     routines:SSL23_GET_SERVER_HELLO:unknown protocol
DEBUG: .../IO/Socket/SSL.pm:669: fatal SSL error: SSL connect attempt failed error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol
DEBUG: .../IO/Socket/SSL.pm:1769: IO::Socket::INET configuration failed
DEBUG: .../IO/Socket/SSL.pm:2588: free ctx 61267216 open=61267216
DEBUG: .../IO/Socket/SSL.pm:2593: free ctx 61267216 callback
DEBUG: .../IO/Socket/SSL.pm:2600: OK free ctx 61267216
500 Can't connect to 64.31.22.131:7808
Content-Type: text/plain
Client-Date: Fri, 09 Jan 2015 10:15:19 GMT
Client-Warning: Internal response

Can't connect to 64.31.22.131:7808

LWP::Protocol::https::Socket: SSL connect attempt failed error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol at E:/Perl64/lib/LWP/Protocol/http.pm line 49.

根据 Stefan 的建议，我使用 http:// 作为代理地址（而不是 https），这产生了一些更好的结果，如下所示，它在 Ubuntu 下完美运行，但在 Windows 中却不行......

DEBUG: .../IO/Socket/SSL.pm:2555: new ctx 65664688
DEBUG: .../IO/Socket/SSL.pm:1354: start handshake
DEBUG: .../IO/Socket/SSL.pm:563: ssl handshake not started
DEBUG: .../IO/Socket/SSL.pm:599: not using SNI because hostname is unknown
DEBUG: .../IO/Socket/SSL.pm:650: set socket to non-blocking to enforce timeout=120
DEBUG: .../IO/Socket/SSL.pm:663: Net::SSLeay::connect -> -1
DEBUG: .../IO/Socket/SSL.pm:673: ssl handshake in progress
DEBUG: .../IO/Socket/SSL.pm:683: waiting for fd to become ready: SSL wants a read first
DEBUG: .../IO/Socket/SSL.pm:703: socket ready, retrying connect
DEBUG: .../IO/Socket/SSL.pm:663: Net::SSLeay::connect -> -1
DEBUG: .../IO/Socket/SSL.pm:673: ssl handshake in progress
DEBUG: .../IO/Socket/SSL.pm:683: waiting for fd to become ready: SSL wants a read first
DEBUG: .../IO/Socket/SSL.pm:703: socket ready, retrying connect
DEBUG: .../IO/Socket/SSL.pm:663: Net::SSLeay::connect -> -1
DEBUG: .../IO/Socket/SSL.pm:673: ssl handshake in progress
DEBUG: .../IO/Socket/SSL.pm:683: waiting for fd to become ready: SSL wants a read first
DEBUG: .../IO/Socket/SSL.pm:703: socket ready, retrying connect
DEBUG: .../IO/Socket/SSL.pm:663: Net::SSLeay::connect -> -1
DEBUG: .../IO/Socket/SSL.pm:673: ssl handshake in progress
DEBUG: .../IO/Socket/SSL.pm:683: waiting for fd to become ready: SSL wants a read first
DEBUG: .../IO/Socket/SSL.pm:703: socket ready, retrying connect
DEBUG: .../IO/Socket/SSL.pm:2411: ok=1 cert=69181312
DEBUG: .../IO/Socket/SSL.pm:2411: ok=1 cert=69943488
DEBUG: .../IO/Socket/SSL.pm:2411: ok=1 cert=69943136
DEBUG: .../IO/Socket/SSL.pm:1559: scheme=www cert=69943136
DEBUG: .../IO/Socket/SSL.pm:1569: identity=www.comparis.ch cn=www.comparis.ch alt=2 www.comparis.ch 2 it.comparis.ch 2 en.comparis.ch 2 fr.comparis.ch
DEBUG: .../IO/Socket/SSL.pm:663: Net::SSLeay::connect -> -1
DEBUG: .../IO/Socket/SSL.pm:673: ssl handshake in progress
DEBUG: .../IO/Socket/SSL.pm:683: waiting for fd to become ready: SSL wants a read first
DEBUG: .../IO/Socket/SSL.pm:703: socket ready, retrying connect
DEBUG: .../IO/Socket/SSL.pm:663: Net::SSLeay::connect -> 1
DEBUG: .../IO/Socket/SSL.pm:718: ssl handshake done
DEBUG: .../IO/Socket/SSL.pm:2588: free ctx 65664688 open=65664688
DEBUG: .../IO/Socket/SSL.pm:2593: free ctx 65664688 callback
DEBUG: .../IO/Socket/SSL.pm:2600: OK free ctx 65664688
500 Status read failed:A non-blocking socket operation could not be completed
immediately
Content-Type: text/plain
Client-Date: Fri, 09 Jan 2015 16:49:31 GMT
Client-Warning: Internal response

Status read failed: A non-blocking socket operation could not be completed immediately
at E:/Perl64/lib/Net/HTTP/Methods.pm line 276.

我想现在有点不同了，但是我在网上搜索过，找不到任何答案。

【问题讨论】：

您的代码从这里开始工作（不使用 ActivePerl）。并且 SSLv3 不起作用，因为服务器只支持 TLS1.0。您能否使用perl -MIO::Socket::SSL=debug4 program.pl 运行您的代码并将输出添加到您的问题中？
我已用所需信息更新了帖子。
"500 无法连接到 192.3.121.204:3128 (10060)" - 看起来它无法连接到您指定的代理。 10060 是 WSAETIMEDOUT，即与代理的连接因超时而失败。
它是第一个代理，第二个说 LWP::Protocol::https::Socket: SSL 连接尝试失败错误：140770FC:SSL 例程：SSL23_GET_SERVER_HELLO:unknown protocol
是的，我看的不够近。

标签： perl proxy

【解决方案1】：

我想我明白你的问题是什么了。当您执行 https 代理请求时，您不是使用 HTTP 协议连接到代理，而是使用 HTTP 协议，然后发出 CONNECT 请求来构建隧道。所以代理的 URL 必须是 http:// 而不是 https://：

$ua->proxy(['https'],'http://199.200.120.140:8089');
                      ^^^^ http:// instead of https://

除此之外，请确保 LWP::UserAgent 和 LWP::Protocol::https 至少为 6.06 版本，因为它们为代理 HTTPS 流量添加了适当的支持。但我认为在你的情况下版本应该足够新。

编辑：由于您使用最新版本的 IO::Socket::SSL 在 Windows 上运行代码，因此您触发了与 Windows 中新添加的对非阻塞 SSL 套接字的支持相关的错误，这会导致“状态读取失败：无法立即完成非阻塞套接字操作”。有关详细信息和修复，请参阅https://github.com/libwww-perl/net-http/pull/11。

【讨论】：

是的，现在好多了。我也尝试过这种组合（没有想太多），但由于结果相同（没有调试），我没有提到它。我现在在我的线程中更新了输出。
我猜是windows的功能，刚刚在VM Player/Ubuntu下试了一下，没问题。
请查看 LWP::UserAgent、LWP::Protocol::https 和 IO::Socket::SSL 的版本，例如 perl -MIO::Socket::SSL -e 'warn IO::Socket::SSL->VERSION' 和其他版本相同。两个 LWP 包都应该至少为 6.06，但我也有兴趣查看 IO::Socket::SSL ActiveState 的版本。
LWP::UserAgent 是 6.09 LWP::Protocol::https 是 6.09 IO::Socket::SSL 版本是 2.008
LWP::Protocol::https 的最新版本是 6.06，所以我猜这就是你的意思？除此之外，一切都是相当新的，本身不应该引起问题，也就是说，它应该提供正确的代理支持。尽管带有非阻塞的错误消息可能指向最近更改 IO::Socket::SSL 导致的问题，以便在 Windows 上也具有非阻塞工作。我需要仔细看看这个。

【解决方案2】：

感谢 Steffen，解决方案在那里 https://github.com/libwww-perl/net-http/pull/11 我试过了，它在我的情况下工作得很好。

【讨论】：