[Waragainstsleep]

Has anyone had any luck sharing folders to iOS over webDAV from a Lion Server? I've tried on a couple and it just doesn't seem to work.

[besson3c]

What is going on? I don't use Lion Server, but WebDAV is WebDAV. You can trace WebDAV problems in Lion the same way you would any other OS running the same web server.

[Waragainstsleep]

Specifically its WebDAV file shares. Basically you have a tickbox for each of your shares for each protocol you want to use. One of them is labelled "Share with iOS devices" or similar, but it means WebDAV.

Supposedly you can then connect using Command-K from another Mac and http://X.X.X.X/webdav/user though I haven't gotten this to work at all. I have persuaded it to prompt for login credentials using http://X.X.X.X/ or sometimes http://X.X.X.X/user and for certificates using SSL but regardless it eventually gives you a totally useless "there was an error" or "IP is wrong" error message and Console reports that WebDAV is not supported for that share.

I've checked the Apache config files, the various WebDAV config files and the virtual host settings, everything I can find looks like its properly set but nothing will successfully connect to it via WebDAV. The only thing both servers have in common is they were upgraded from Snow Leopard Server. I supposed I ought to try with a clean one just in case.

[besson3c]

If SSL is required the URL should start with https://

Is the web server responding on port 80? What are your Apache error logs saying? Can you paste in your Apache WebDAV config?

[ChockyII]

Here's what I've figured out so far:

1. Make sure your DNS is working (forward and reverse)
2. If you have more than one realm configured on the server use the appropriate domain name rather than the server IP address.
3. Use SSL (https://your.server.name/webdav)
   

I was able to get things working without SSL in some applications but others (Pages, and Numbers, for example) would appear to copy the file but the file on the server would be zero bytes. Switching to https solved the problem.

Hope that helps.