Forum OpenACS Q&A: Problems with Oacs WebDAV and a Macbook

1: Problems with Oacs WebDAV and a Macbook

Posted by Richard Hamilton on 08/19/11 04:29 PM

Can anyone help me with the following problem with openacs WebDAV enabled Filestore?

1) Works perfectly using Netdrive
2) Works perfectly using WebDAV Navigator on the iPhone
3) Fails with Macbook using OSX

Specifically, the user can see the correct file directory and navigate and view its contents. The user can add a folder, but all attempts to upload a file cause the following error:

The Finder can’t complete the operation because some data in “file.jpg” can’t be read or written.
(Error code -36)

I also have an extra '/' in my WebDAV url which I cannot see an obvious way to correct using the parameter settings. Before I go hacking at the code like a bull in a china shop, is this a bug or have I made an error in configuration?

https://63.246.8.12:8440/dav/dropbox//pages/file-storage_4983/documents

Could that be what is causeing the Mac to choke?

Regards
Richard

2: Re: Problems with Oacs WebDAV and a Macbook (response to 1)

Posted by Richard Hamilton on 08/20/11 02:43 PM

Ok, have realised that the spurious leading '/' should be removed in the service.tcl config file rather than in a parameter. Awaiting further feedback from Macbook user!

Regards
Richard

3: Re: Problems with Oacs WebDAV and a Macbook (response to 1)

Posted by Richard Hamilton on 09/06/11 06:24 PM

Doesn't work. Seems to be a bug with WebDAV support in recent versions of Mac OSX. Does anyone have any experience of this or know any workarounds to get OpenACS WebDAV support working with a Macbook?

Regards
Richard

4: Re: Problems with Oacs WebDAV and a Macbook (response to 1)

Posted by Jeff Rogers on 09/08/11 06:28 AM

I found a few suggestions that the finder webdav client sends files with chunked transfer-encoding, which I don't believe AOLServer decodes for entity bodies. If so, this is probably not easily fixable from the dav code, since by the time the dav code gets control the request has already been read (or more likely, not read in this case).

Are you seeing any error messages in your server log? Or the request log might show some kind of error status on the webdav PUT request.