I did it. I was able to get the Apache mod-dav to work. The end result is sort of a mess with Apache folders strewn out all over the system in various odd places, but it works. First I got Apache running as a simple web server and confirmed I could access it from Linux, Windows Vista, and Windows XP systems on my network. Just accessing it on my 192.168.1.x IP address, no DNS name. Then I set up the web-dav module using the config file in /etc/httpd/extra and was able to access the web folder using Dolphin on Linux, and by mapping a network drive from the Vista system. XP didn't work at first. I learned that while FollowSymLinks works for accessing folders that are logically in the document root path but are actually outside of it in the physical heirarchy, those directory names won't match the document root directory container definition that the Options Indexes directive applies to. That's maybe not the best way to say it, but suffice it to say that I had to put another Options Indexes directive in the container for the WebDAV directory to get around a 'Directory index forbidden by Options directive' error. I couldn't get Win XP to access the WebDAV folder at all. I think it is a problem with the web folder redirector on XP. I read that using SSL causes XP to authenticate differently, so I enabled mod-SSL using the config provided in /etc/httpd/extra. That was a much more involved effort than doing the mod-dav WebDAV folder setup. SSL is not too difficult to understand conceptually, but getting it set up properly is rather complicated. I would have had an awful time of it had it not been for this excellent link that describes how to create a self-signed certificate. Once I got my apache server configured for SSL, I was able to create a network place in XP to map the WebDAV folder. Somewhere I'm hitting a file size limit of 2 GiB. I can copy files to the WebDAV folder from other systems so long as it is 2 GiB or smaller. If the file exceeds that size, I get an error and the file won't copy.
Setting Up Your WebDAV Server. To set up your WebDAV server to comply with SOTI Hub requirements: Perform these actions in the Microsoft Internet Information Services (IIS) Manager. The application pool for the WebDAV server must have Read, Write, and List.