> -----Original Message----- > From: [email protected] [mailto:curl-library- > [email protected]] On Behalf Of Daniel Stenberg > Sent: Wednesday, December 08, 2010 2:20 PM > > On Wed, 8 Dec 2010, Hu, Eric wrote: > > > So, the data coming back from tests 301 and 306 are fine. The > problem is > > axTLS is reporting a "close notify" alert as an error, so cURL > returns a > > non-0 value. This can only be fixed in axTLS, as the data/payload > portion > > of the "close notify" packet are not passed up to the caller for > inspection > > and the error code (same one reported in tests 311 and 312) is too > generic > > to interpret. > > 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. Eric ------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
