Re: [Bug-wget] GNU wget 1.15 released

[Ray Satiro]

On 1/22/2014 6:10 PM, Gisle Vanem wrote:
> I've built Wget (for many years) with all protocols enabled. And I 
> already have a 'ca-certificate' in my wgetrc-file. https works fine:
>
>  wget -d  https://encrypted.google.com
>
> DEBUG output created by Wget 1.15.00 (MingW) on Windows_NT.
> ...
> Initiating SSL handshake.
> seconds 900.00, Winsock error: 0   << !! this annoying stuff seems to 
> be caused by gnulib too.
> Handshake successful; connected socket 3 to SSL handle 0x00e336e8
> certificate:
>  subject: /C=US/ST=California/L=Mountain View/O=Google 
> Inc/CN=*.google.com
>  issuer:  /C=US/O=Google Inc/CN=Google Internet Authority G2
> X509 certificate successfully verified and matches host 
> encrypted.google.com
Yeah I'm getting a flood of that when I -d https
seconds 900.00, Winsock error: 0
seconds 900.00, Winsock error: 0
seconds 900.00, Winsock error: 0
seconds 900.00, Winsock error: 0
seconds 900.00, Winsock error: 0
seconds 900.00, Winsock error: 0
seconds 900.00, Winsock error: 0
over and over

I tried a build I have from last year (82126cc) and I'm not seeing it 
there. The debug lines are from run_with_timeout() in src/mswindows.c 
and they've been there quite a while according to git blame so some 
behavior has changed and that's calling run_with_timeout() a lot. Or 
maybe not? I'm not seeing extra thread spawns in process explorer. If 
anyone is interested in pursuing this I suggest git bisect.

Jay