Unfortunately this is a known critical issue which I have had great difficulty in solving:<div><br></div><div><meta http-equiv="content-type" content="text/html; charset=utf-8"><a href="https://github.com/matburt/mobileorg-android/issues/22">https://github.com/matburt/mobileorg-android/issues/22</a></div>

<div><br></div><div><a href="https://github.com/matburt/mobileorg-android/issues/22"></a>The workaround in the case of <a href="http://mydisk.se">mydisk.se</a>, to say nothing of whether this would be acceptable to you, is to use the non-https version of the <a href="http://mydisk.se">mydisk.se</a> webdav system.  This is actually the first I have heard that mydisk&#39;s https has issues with Android&#39;s certificate system.</div>

<div><br></div><div>I suspect there is some final solution to this problem, but I&#39;m still working on it... I&#39;d recommend adding a note to that bug I just posted above with the details that you have listed here and when I close it (hopefully for the 0.6.0 release) you will be notified of it.<br>

<br><div class="gmail_quote">On Tue, May 10, 2011 at 3:31 PM, Robert Goldman <span dir="ltr">&lt;<a href="mailto:rpgoldman@sift.info">rpgoldman@sift.info</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

<div class="im">On 5/10/11 May 10 -12:34 PM, Matthew Jones wrote:<br>
&gt; Hi Robert... I&#39;m the developer for MobileOrg on Android, we have a known<br>
&gt; issue with self-signed certificates.   What version of MobileOrg are you<br>
&gt; using?  If you visit the site in the Android browser do you get a<br>
&gt; certificate notification also?<br>
<br>
</div>Yes, I do, but I get the opportunity to continue through the certificate<br>
notification.<br>
<br>
this is android 2.2<br>
<br>
Best,<br>
<font color="#888888">r<br>
<br>
<br>
</font></blockquote></div><br></div>