Hello everyone, 2013/2/4 Daniel Stenberg <[email protected]> > I need a little help from someone with decent Windows knowledge to comment on > and massage this issue!
Daniel, thanks for the separate hint on this issue. Otherwise I probably would have overlooked it. > winsspi ssl engine was unable connect through ssl with curl build with > winsspi(no openssl): [...] > this error occured only on some specific machine: win7 without sp1 > maybe it's related to http://support.microsoft.com/kb/975858 [...] > and the problem has gone. i don't now if CURL really need specify > ISC_REQ_EXTENDED_ERROR cause it's not related to client side; I don't think the flag is actually required by curl itself, but from the following description I though it was a good idea to use it: > ISC_REQ_EXTENDED_ERROR > When errors occur, the remote party will be notified. Source: http://msdn.microsoft.com/en-us/library/windows/desktop/aa375924.aspx It may be related to the issue/hotfix you linked above. I don't know if using the flag actually brings any benefit to curl, so I would suggest to remove it for now. It might improve the way a connection is closed in case of an error, but thanks to the TCP-layer that should not be a problem. I am going to push a commit to the repository that completely removes the flag. Best regards, Marc ------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
