Cpanel WebDisk & Weave

[balaji]

Hi there,

Since Google Browser Sync no longer works with Firefox 3, I thought I would give the new Weave extension from Mozilla a try.

The Weave extension apparently works with your own WebDAV server so I thought I would set it up using the Webdisk option. So far however, I'm not having much luck.

I've posted about this over on the Mozilla forums but there isn't much response, so I thought I might try asking here - since folks here have the added advantage of knowing the WebDisk feature better

If anyone has tried this and got it to work, please let me know how - I can post error logs and other such info if required.

[areidmtm]

I tried Weave (never with webdav) and it never worked quite right nor would it connect half the time.

I got rid of it and now using Foxmarks.

[nitrocrzy]

I couldn't even find Weave... giving Foxmarks a try.....

[balaji]

I tried Weave (never with webdav) and it never worked quite right nor would it connect half the time.

I got rid of it and now using Foxmarks.

The new version 0.2.5 is getting pretty decent reviews for stability & performance (if you switch off tab syncing).

I would move to Foxmarks but I need history & cookie syncing as well and right now Weave is the only thing out there.

[nitrocrzy]

The new version 0.2.5 is getting pretty decent reviews for stability & performance (if you switch off tab syncing).

I would move to Foxmarks but I need history & cookie syncing as well and right now Weave is the only thing out there.

I'll keep trying on Weave... the problem is they apparently are not taking any new registrations at this time

[balaji]

I'll keep trying on Weave... the problem is they apparently are not taking any new registrations at this time

Yup I've been waiting for them to re-open registrations for a while now, but got tired of waiting and decided I would be better trying to get my own install working..

[unlox775]

Hi, I just tried to get Weave to work using my (HostMonster which is also BlueHost account's Web Disk feature. First I followed Marios Tziortzis instructions here:

http://marios.tziortzis.com/page/blo...n-your-server/

with a few exceptions: 1) Instead of his username example (user123), I had to use the host name as well (e.g. user123@mydomain.com) wherever he said to use the username. 2) make sure to use cPanel's insecure URL version as Weave doesn't like the certificate mismatch (it's OK, Weave does it's own encryption)

At first it looked like it just didn't authenticate, because in the "Sign In.." dialog, it would say invalid username / password. But if you look at the advanced activity log, you could see it would log in, make the "user/user123@mydomain.com/" dir in my WevDAV root, check if (user/user123@mydomain.com/) "meta/version" exists, if it didn't exists then it would try to make a "meta" directory using the DAV request: MKCOL. The server would reply with a response: 200, which is wrong. It shoud respond with a "201" which means the "collection" was successfully created...

Anyhow, I hacked around a bit and did the following:

made my own "user/user123@mydomain.com/meta/version" file with just a string "0.2.6" in it
made a directory "user/user123@mydomain.com/public" directory

(maybe some other hacks, as well...)

But now I get the "Sign In..." to work and when it sync's it instantly says the sync suceeded. However internally it's erroring out with this message:

2008-08-11 16:02:46 Service.DAV DEBUG LOCK request for lock
2008-08-11 16:02:46 Service.DAV ERROR Could not acquire lock

The HTTP actitivity shows this request content:

<?xml version="1.0" encoding="utf-8" ?>
<D:lockinfo xmlns="DAV:">
<D:locktype><D:write/></D:locktype>
<D:lockscope><D:exclusive/></D:lockscope>
</D:lockinfo>


And the response is:

HTTP/1.x 200 OK

Date: Mon, 11 Aug 2008 22:25:31 GMT

Server: cPanel

Content-Length: 0

Connection: Keep-Alive

Keep-Alive: timeout=15, max=100


Response 200 is right for the LOCK DAV Method, but it should return "the value of the lockdiscovery Field" in the response instead of an empty response body.

So in general this seems to be the failings of cPanel's WebDAV implementation:

1) A MKCOL method should never return status 200
2) A LOCK method should return status 200, but it needs to return something in the response, or use the status 201 meaning it created a new lock

I hope this helps someone. I'd like to use the WebDAV implementation of Weave myself... I'll probably just end up installing DAV on my own server... (grumble grumble)