> From: Daniel Stenberg
> Sent: Wednesday, January 12, 2011 1:37 PM
> Subject: RE: axTLS patch set
>
> On Wed, 12 Jan 2011, Hu, Eric wrote:
>
> > Really? (I suppose I could just look at the code) I'm surprised the
> easy
> > interface worked then. If the axTLS code sees "read" return -1, it
> assumes
> > the connection is lost, even if errno==EAGAIN. Maybe all of my tests
> were
> > with very fast servers that responded very quickly.
>
> Well, most (all?) of the easy interface does recv after having done
> select on
> the socket to figure out if there's a chance of anything to read so
> quite
> possibly it never causes a problem...
>

To be safe(r), should we use the easy interface for HTTPS with axTLS,
instead of our current use of multi? I still can't believe we
haven't seen this issue pop up using multi.

(I haven't done additional investigation, because I have moved to
another work site and project that doesn't use libcurl+axTLS, but I
still help out on the old project.)

I'll also go check out the new axTLS mailing list. Thanks.

Gary @ Broadsoft

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2011-01-12