> > On Wed, 8 Dec 2010, Hu, Eric wrote: > > > > > So, the data coming back from tests 301 and 306 are fine. > > > > Please try asking the axTLS team first to see how they view this > issue. > > > Ok, it's posted as a bug to axTLS. There's not a whole lot of activity > on their SourceForge page, but hopefully it'll get someone's attention. > > As I wrote up the bug report, I realized I wasn't exact in describing > the problem above. When axTLS gets a close_notify, it actually doesn't > report an error, but doesn't report that it got the alert either. This > leads the caller to try reading again on a closed connection, which is > what leads to cURL's return code being non-zero. > Ok, a patch has been submitted to axTLS (http://sourceforge.net/tracker/?func=detail&aid=3132700&group_id=171217&atid=857113). Applying this patch to axTLS 1.2.7, applying the patches that started this thread to cURL and linking the results will result in a cURL that passes tests 301 and 306.
Eric ------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
