Can't get WebDAV to work properly

Well, first a few things I've figured out. I'm not exactly certain they're completely necessary, but the *@&!^$# thing started working after I did this.

1. The username is capitalized exactly as it shows up in Frontview. E.g., "JohnDoe" rather than "johndoe" or "JOHNDOE." I think all the Unix systems and all Internet protocols I've worked with (over the past 40+ years) either have been case-insensitive for user names or have had a two-username system, with one being form ("John Doe") and one being all lowercase and actually used for naming the user's root directory ("johndoe"). So if I'm right about this, it's somewhat unusual.
2. I rebooted the ReadyNAS before it started working. So maybe rebooting it was necessary.
3. Initially I had particularly high security for the WebDAV share: very strong passwords, explicit permissions for different categories of users, only specific users having write permissions, etc. I've relaxed them temporarily until the system has all the functionality I need. This mainly means working from different locations, with different devices, and using a specific set of apps with the share. Once I'm satisfied the share is working how I want it to, I will restore the security settings one-by-one and check that each restoration doesn't break connectivity.

Otherwise, JennC's post, along with what I've said above, solves the problem.

Here are some miscellaneous comments to suggest ways to make this easier for others who might run into similar problems:

1. Either Netgear never had documentation for setting up WebDAV for OS4, or it was deleted when OS6 came out. Provide and continue to provide appropriate documentation for all versions of the OS. "OS6" suggests that there have been 6 versions of the OS, but I doubt that all of them have handled WebDAV differently. So there probably would only need to be 2-4 versions of the documentation for WebDAV.
2. Ditto, for target operating systems. The one in Jenn's link is only for Windows. Maybe Netgear assumes people running Linux, OS X, IOS, Android, or Chrome don't need such hand-holding. A Linux explanation would convey the most fundamental information since the ReadyNAS and WebDAV architectures are Unix-based. A generic version without specific reference to a particular OS would also helpfully convey the sequence of steps and things like naming conventions, path components, etc. Here's an example of headings for a generic summary:
1. Authorize a HTTP/S share to use WebDAV and set permissions for the share
2. Set router for remote access (set external domain name or IP address and set port 80 and/or 443 forwarding )
3. Set up client system to access the share via WebDAV
4. (Optional) Set up client system to mount the share automatically upon login (or startup)
5. (Optional) On each client system, set the path to the share, with appropriate subdirectories if necessary, in each application that will routinely use the share by default.
3. The documentation should be more clear about case-sensitivity, etc. AFAIK, it doesn't say anything about such issues.
4. A brief discussion of the protocol would be helpful. I had to read about WebDAV at Wikipedia and elsewhere to learn that it's a file-system protocol built on HTTP. Only once I understood this did I understand why the WebDAV option is only under HTTP/S. Mentioning this in the documentation would save time for users, like myself, whose prior exposure to WebDAV has only been retrieving a URL and connecting to it.
5. Ditto for the fact that WebDAV applies to shares. As someone familiar with Unix, it helped to understand that the root directory of a share is used as a mount point and that multiple volumes (shares) can be mounted as distinct WebDAV file systems.
6. Based on #5, I could understand that the WebDAV path needed the (case-sensitive) share name as the last part of the path. But I don't think most potential users would make this leap. It wouldn't hurt to say this explicitly in a sentence or two.
7. Both the software and documentation need to deal with where to get and how to install SSL certificates.

I learned quite a bit from this process, but I really just needed to get WebDAV up and working. We shouldn't need to search the Internet for days to figure this out.