Hi,

just testing curl-7.9.3-pre1...

First, it happens that curl finishes with an error but without an error
message. Could it be that this is the case if the timout occurs during
dns lookup?

    # curl -v --connect-timeout 1 https://meine.db24.de
    * Closing connection #0
    curl: (28)

Second, reading from an SSL-connection does not work correctly. I think
that libcurl now immediately returns from an SSL_read, because the socket
is no longer blocking:

    $ curl -v -t 30 https://meine.db24.de/mod/WebObjects/db24.woa/474/wo/CtjdV4wwhrKG3JVkjgE0ifH8Ko8/0.0.FrameMain.7
    * SSL connection using RC4-MD5
    * Server certificate:
    * subject: /C=DE/ST=Hessen/L=Frankfurt/O=Deutsche Bank AG/OU=Deutsche Bank 24 AG/OU=Terms of use at www.verisign.com/RPA (c)00/CN=mein
    e.db24.de
    * start date: 2001-06-13 00:00:00 GMT
    * expire date: 2002-07-13 23:59:59 GMT
    * common name: meine.db24.de (matched)
    * issuer: /O=VeriSign Trust Network/OU=VeriSign, Inc./OU=VeriSign International Server CA - Class 3/OU=www.verisign.com/CPS Incorp.by
    Ref. LIABILITY LTD.(c)97 VeriSign
    * Connected to meine.db24.de (193.150.167.1)
> GET /mod/WebObjects/db24.woa/474/wo/CtjdV4wwhrKG3JVkjgE0ifH8Ko8/0.0.FrameMain.7 HTTP/1.1
    User-Agent: curl/7.9.3-pre1 (i686-pc-linux-gnu) libcurl 7.9.3-pre1 (OpenSSL 0.9.6)
    Host: meine.db24.de
    Pragma: no-cache
    Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, */*

    * Closing connection #0
    curl: (18) transfer closed with 2465 bytes remaining to read

You can test this by calling https://meine.db24.de/ and following the
redirects and frames in the resulting html-code.

Bye,
Georg
Received on 2002-01-08