20 May
2013
20 May
'13
11:17 a.m.
On 05/20/2013 02:17 AM, Ján Máté wrote:
On May 20, 2013, at 2:50 AM, Ken Murchison
<murch(a)andrew.cmu.edu> wrote:
OK, the quickest way for me to do this was to give you a test account on
my home dev machine:
host: https://ksmurchison.dyndns.org/dav/principals/user/test01/
passwd: test01
BTW, rather than having the admin specify the path to user principals in
config.js, you should look into doing your discovery by doing a PROPFIND
on /.well-known/caldav for DAV:current-user-principal, and following any
redirects. See http://tools.ietf.org/html/rfc6764
--
Kenneth Murchison
Principal Systems Software Engineer
Carnegie Mellon University
I applied the caldavzap patch and the client got
further along. It sees my calendars but spins trying to load them. The last request that
I see if a sync-collection report. I can send telemetry of the request in the morning if
you like. I *might* be able to get you access to a test account.
The fastest way
to find the root of the problem is a test account.