Webdav Plugin 2.0b2 crashes on Sharepoint

[brotbuexe]

Hi,

I tried a sharepoint webdav and all I get is a crash (same crash on the old version on tc 1). The path and login works with "FolderSync".

The log:

2012-11-11 10:18:33 WebDAV:LIST /
2012-11-11 10:18:38 WebDAV:properties /mysite shared
2012-11-11 10:18:50 WebDAV:LIST /
2012-11-11 10:18:51 WebDAV:open /mysite shared
2012-11-11 10:18:52 WebDAV:LIST /mysite shared/personal/username/
2012-11-11 10:18:52 WebDAV:CONNECT mysite shared
2012-11-11 10:18:52 WebDAV:Cert subject: CN=*.host.de,OU=Domain Control Validated - RapidSSL(R),OU=See www.rapidssl.com/resources/cps (c)11,OU=GT123,O=*.host.de,C=DE,2.5.4.5=#somelongnumber
2012-11-11 10:18:52 WebDAV:Cert issuer: CN=RapidSSL CA,O=GeoTrust\, Inc.,C=US

Only this line in the sharepoint iis log:

2012-11-11 09:27:07 192.168.5.23 PROPFIND /personal/username/ - 443 - 123.4.5.6 ezdavplugin/2.0beta2+TotalCommander/2.0beta4+(Android;+en_EN) 401 2 5 93

So there is no login.

Dont know if its the wild card ssl certificate, but this cert is working with the ftp plugin when connecting to a IIS FTP.

[ghisler(Author)]

Error 443 is "access denied". I guess that your server is using active directory or some other Microsoft-specific authentication scheme not supported by Androids apache http client (used by my plugin).

[brotbuexe]

Error 443 is "access denied". I guess that your server is using active directory or some other Microsoft-specific authentication scheme not supported by Androids apache http client (used by my plugin).

443 is the port number. If you mean 401 I think this would be okay because normally a client would first try without login and would get a 401 with a challenge response to know what login methods are possible? Don't know how the android client works.

http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html

But why would it just crash?

I don't need the plugin. It was more like a try and forget I have it.
If it's okay for you we could just forget about it...

[ghisler(Author)]

It shouldn't. The last crash report on Google Play for this plugin is from May 28, 2012. Did you try to send the crash report to Google?