B
Brian Lalonde
The WinHTTP object has enormous granularity in ignoring specific SSL errors.
SslErrorFlag_UnknownCA = 256,
SslErrorFlag_CertWrongUsage = 512,
SslErrorFlag_CertCNInvalid = 4096,
SslErrorFlag_CertDateInvalid = 8192,
SslErrorFlag_Ignore_All = 13056
This allowed me, for example, to declare ahead of time that a
nonmatching CName in the certificate should be ignored.
The HttpWebRequest .NET class seems only to provide a
SecureChannelFailure value to the Status of a WebException.
This seems require that anticipated errors may not be preset to ignore,
and more importantly, that an invalid CName error cannot be
distinguished from an invalid date, unknown authority, or wrong usage
certificate error.
Is this true, or am I missing something?
SslErrorFlag_UnknownCA = 256,
SslErrorFlag_CertWrongUsage = 512,
SslErrorFlag_CertCNInvalid = 4096,
SslErrorFlag_CertDateInvalid = 8192,
SslErrorFlag_Ignore_All = 13056
This allowed me, for example, to declare ahead of time that a
nonmatching CName in the certificate should be ignored.
The HttpWebRequest .NET class seems only to provide a
SecureChannelFailure value to the Status of a WebException.
This seems require that anticipated errors may not be preset to ignore,
and more importantly, that an invalid CName error cannot be
distinguished from an invalid date, unknown authority, or wrong usage
certificate error.
Is this true, or am I missing something?