NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
thampton
May 19, 2010Aspirant
Cannot upload files using https in IE
hi, My preferred method to upload and download files remotely is using a web browser and https. I can access my shares OK but cannot upload. A colleague of mine also has a ReadyNAS Duo and he ha...
Sandshark
Dec 30, 2011Sensei
OK, here I am again resurrecting an old thread. But just in case someone searches and trys this, it won't work anymore (at least, doesn't for me). I've had two firmware changes since I posted my solution here and who knows how many other configuration changes, including a factory default to allow 2GB drives. I have no idea when it broke. Turns out nobody had been using WebDAV to access my server for a while because it's broken in Win 7. But when finally sombody tried using WebDrive, it seemed to work but the files retrieved were just copies of the .html for the file manager interface, not the files themselves. It took me a bit to figure out that it wasn't a WebDrive issue.
But, there is another solution. What you have to do is create a separate alias for the share, enabling WebDAV in one alias and the HTTP(S) file manager in the other. I again put this in a separate .conf file in Addons so it won't get erased by configuration changes, but you can put it in something that will get overwritten with a firmware re-install if you want more safety.
So, where Shares,conf contains the following:
My separate .conf file contains this:
So, "Family" with an upper case F is an alias to 'family", with "Family" having WebDAV access and the "family" having HTTP(S) access via the File Manager. (I have it restriced to HTTPS only elsewhere).
Note that I am using share access on this NAS, so what is in your Shares.conf may be a little different. Just duplicate eveything except the share name and Perl directives, replacing with your altername name and "Dav On". If using share access mode, be sure to NOT change the name of the user.
But, there is another solution. What you have to do is create a separate alias for the share, enabling WebDAV in one alias and the HTTP(S) file manager in the other. I again put this in a separate .conf file in Addons so it won't get erased by configuration changes, but you can put it in something that will get overwritten with a firmware re-install if you want more safety.
So, where Shares,conf contains the following:
Alias "/family" "/c/family"
<Location "/family">
Options Indexes
Order allow,deny
Allow from all
Require user "family"
AuthType Basic
AuthName "My Shares"
SetHandler perl-script
PerlHandler Apache::FileManager
</Location>
My separate .conf file contains this:
Alias "/Family" "/c/family"
<Location "/Family">
Options Indexes
Order allow,deny
Allow from all
Require user "family"
AuthType Basic
AuthName "My Shares"
Dav On
</Location>
So, "Family" with an upper case F is an alias to 'family", with "Family" having WebDAV access and the "family" having HTTP(S) access via the File Manager. (I have it restriced to HTTPS only elsewhere).
Note that I am using share access on this NAS, so what is in your Shares.conf may be a little different. Just duplicate eveything except the share name and Perl directives, replacing with your altername name and "Dav On". If using share access mode, be sure to NOT change the name of the user.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!