Thanks for the reply. I guess my issue is that I don't understand how these urls are being formed. The client application in this case is Transmit which is an FTP app that supports webdav. My assumption has been that the url is formed on the server end via Apache. Also, the Finder (file browser) in OS X supports webdav and reports the same url with double slashes. So it appears that it doesn't matter what is the client. I suppose it could be an OS issue. This is a very simple webdav share. No scripts or anything fancy. It is basically just a file repository. There is no access via Web Browser. (Options -Index). We are a music publishing company and have about 25 users who use the server for collaboration purposes. For the most part everything works fine. But a few of the users cannot download the target file unless a slash is removed. Of course, they don't want to have to remember to do that, they just want it to work. I realize now that when I posted I used "hostname" in the url description, but really should substitute "sharepoint" for "hostname". ie. http://sharepoint.mydomain.com shows up as http://sharepoint.mydomain.com. Not sure that really makes any difference, but might help in understanding the setup. Best, Tim Roberts, Vibe Room Music Nashville, TN On Dec 4, 2011, at 12:17 AM, Steve Swift wrote: I'm no expert in this area, which is perhaps why I've also seen the problem. The upside is that apache seems to ignore the double slashes, but this is probably because the underlying systems do the same. Try typing a file, then change one of the slashes to a double slash; it still types out (both Windows and Linux). |