Disabling these checks worked gloriously under WinHttp 5.0, but 5.0 is
dead. It is inconceivable that I am the only person to face this
problem. Can anyone give me any information about how to get around
this?
Actually I'm working with old IIS with self-signed certificate and WinHttp
5.1 but it works good.
I use
DWORD dwOptions =
SECURITY_FLAG_IGNORE_CERT_CN_INVALID
| SECURITY_FLAG_IGNORE_CERT_DATE_INVALID
| SECURITY_FLAG_IGNORE_UNKNOWN_CA
| SECURITY_FLAG_IGNORE_CERT_WRONG_USAGE;
(...)
dwRetVal = WinHttpSetOption( m_hRequest, WINHTTP_OPTION_SECURITY_FLAGS,
&dwOptions, sizeof (DWORD) );
(...)
Do you get an error code ? When do you get error that your server's
certificate is incorrect ?
Marcin Domaslawski
Uzytkownik <jacobth...@gmail.com> napisal w wiadomosci
news:1174498681.8...@n59g2000hsh.googlegroups.com...
I don't get any errors until I call WinHttpSendRequest(), which will
give me an ERROR_WINHTTP_SECURE_FAILURE and what's more, will not hit
the callback function that I've registered for security-related
issues. It just fails and annoys me.