OK, so apparently it was the same certificates issue, just a different error
message. Solution was:
Add:
using System.Security.Cryptography;
using System.Security.Cryptography.X509Certificates;
using System.Net.Security;
( other than X509 these may have already been present - didn't check)
In the class constructor:
ServicePointManager.ServerCertificateValidationCallback = new
RemoteCertificateValidationCallback(DummyCertValidationCb);
and the call back itself:
public static bool DummyCertValidationCb(object sender, X509Certificate
certificate, X509Chain chain, SslPolicyErrors sslPolicyErrors)
{
// we could actually test for a valid certificate here but in this
case
we don't care....
return true;
}
--
View this message in context:
http://mono.1490590.n4.nabble.com/WebRequest-OK-in-NET-fails-in-Mono-tp4660468p4660469.html
Sent from the Mono - General mailing list archive at Nabble.com.
_______________________________________________
Mono-list maillist - Mono-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-list
