I installed a Proxy (Proxy Workbench) and it seems to be some major problems with the communication. When I connected with curl, the connection started with a CONNECT message with the following content:
000000 CONNECT 067 079 078 078 069 067 084 032
000008 login1.s 108 111 103 105 110 049 046 115
000016 wipnet.s 119 105 112 110 101 116 046 115
000024 e:443 HT 101 058 052 052 051 032 072 084
000032 TP/1.0.. 084 080 047 049 046 048 013 010
000040 User-Age 085 115 101 114 045 065 103 101
000048 nt: curl 110 116 058 032 099 117 114 108
000056 /7.9.8 ( 047 055 046 057 046 056 032 040
000064 i386-red 105 051 056 054 045 114 101 100
000072 hat-linu 104 097 116 045 108 105 110 117
000080 x-gnu) l 120 045 103 110 117 041 032 108
000088 ibcurl 7 105 098 099 117 114 108 032 055
000096 .9.8 (Op 046 057 046 056 032 040 079 112
000104 enSSL 0. 101 110 083 083 076 032 048 046
000112 9.7a) (i 057 046 055 097 041 032 040 105
000120 pv6 enab 112 118 054 032 101 110 097 098
000128 led).... 108 101 100 041 013 010 013 010
While the LWP connection attempt started with a POST message:
000000 POST htt 080 079 083 084 032 104 116 116
000008 ps://log 112 115 058 047 047 108 111 103
000016 in1.swip 105 110 049 046 115 119 105 112
000024 net.se/l 110 101 116 046 115 101 047 108
000032 ogin.php 111 103 105 110 046 112 104 112
000040 HTTP/1. 032 072 084 084 080 047 049 046
000048 1..TE: d 049 013 010 084 069 058 032 100
000056 eflate,g 101 102 108 097 116 101 044 103
000064 zip;q=0. 122 105 112 059 113 061 048 046
000072 3..Conne 051 013 010 067 111 110 110 101 t
000080 ction: T 099 116 105 111 110 058 032 084
000088 E, close 069 044 032 099 108 111 115 101
000096 ..Host: 013 010 072 111 115 116 058 032
000104 login1.s 108 111 103 105 110 049 046 115
000112 wipnet.s 119 105 112 110 101 116 046 115
000120 e..User- 101 013 010 085 115 101 114 045
000128 Agent: M 065 103 101 110 116 058 032 077
000136 ozilla/4 111 122 105 108 108 097 047 052
000144 .0 (comp 046 048 032 040 099 111 109 112
000152 atible; 097 116 105 098 108 101 059 032
000160 MSIE 6.0 077 083 073 069 032 054 046 048
000168 ; Window 059 032 087 105 110 100 111 119
000176 s NT 5.1 115 032 078 084 032 053 046 049
000184 )..Conte 041 013 010 067 111 110 116 101
000192 nt-Lengt 110 116 045 076 101 110 103 116
000200 h: 47..C 104 058 032 052 055 013 010 067
000208 ontent-T 111 110 116 101 110 116 045 084
000216 ype: app 121 112 101 058 032 097 112 112
000224 lication 108 105 099 097 116 105 111 110
000232 /x-www-f 047 120 045 119 119 119 045 102
000240 orm-urle 111 114 109 045 117 114 108 101
000248 ncoded.. 110 099 111 100 101 100 013 010
000256 .. 013 010
The content transmitted for the working curl connection was unreadable after the CONNECT message which gave me the impression that the transmission was ciphered. In other words, it seems to me that LWP does not use ciphering (and perhaps also incorrect protocol).
I have searched the man pages for LWP::UserAgent, but can not find anything relevant. Does this help ?
Found the following in man Crypt::SSLeay
LWP::UserAgent has its own methods of proxying which may work for you
+and is likely incompatible with Crypt::SSLeay proxy support.
To use LWP::UserAgent proxy support, try something like:
my $ua = new LWP::UserAgent;
$ua->proxy([qw( https http )], "$proxy_ip:$proxy_port");
At the time of this writing, libwww v5.6 seems to proxy https requests
+ fine with an Apache mod_proxy server. It sends a line like:
GET https://www.nodeworks.com HTTP/1.1
to the proxy server, which is not the CONNECT request that some proxie
+s would expect, so this may not work with other proxy servers than mo
+d_proxy. The CONNECT method is used by Crypt::SSLeayâs internal prox
+y support.
Which makes me even more confused :-/
Best regards
/Johan | 