Cannot upload files using https in IE

I can access my shares OK but cannot upload. A colleague of mine also has a ReadyNAS Duo and he has set his shares up for this access. Only thing is when comparing settings we cannot fathom out how he has managed it and I can't. Where do I need to look to enable this function that I know exists.

Have you enabled read/write access on the share into which you wish to upload?
If you have not, then, do this:

1. Go to Frontview
2. Go the Shares Link
3. Find the share that you wish to upload to.
4. Click on the HTTPS icon. Maybe you have already done this?
5. Enable Read/Write on the share.

See what happens.

I hope this helps.

Thanks for the prompt response,

I have carried out these steps (including Read/Write) which is I believe why I can see the shares using https. Its just that when I click on the share I have no upload option.

Cheers.

I have carried out these steps (including Read/Write) which is I believe why I can see the shares using https. Its just that when I click on the share I have no upload option.

Is this share off of an external USB. What are the contents of this share? Have you tried disabling webdav?

Bang on Spiderman! Seems you cannot have webdav support and https write access at the same time.

Bit of a shame but I guess I will create which access is my preference dependant upon the necessity of the share.

Cheers

Great to have been of help.
:D

Bang on Spiderman! Seems you cannot have webdav support and https write access at the same time.

OK, old thread. But I was here a couple nights ago looking for this information and hoping there was a work-around. Have found no newer thread and I did find a work-around, so here it is.

In order for it to work, you either need to have enabled root SSH access or have an add-on like Xplorer that lets you put files in system folders.

In /etc/frontview/apache/Shares.conf, the HTTP interface is defined. If WebDAV is not enabled, the last lines of the share <Location> data is this:

  SetHandler perl-script
  PerlHandler Apache::FileManager

If WebDAV is enabled, these are replaced with a single line:

  Dav On

The proiblem is, the Dav On replaces the other. But it does work if both are there, as long as Dav On is first.

If you just edit the file and restart Apache, it'll work. At least until you make any change in Frontview to the HTTP/S settings, when it will all get overwritten. So the key is to have a second <Location> area that doesn't get overwritten this way. The perfect place for that is /etc/frontview/apache/addons, which is handled just before Shares.conf. Just make a new .conf file (name doesn't matter as long as you don't overwrite something else) containing the following:

<Location "ShareName">
  Dav On
</Location>

and make sure WebDAV is NOT enabled in Frontview. Of course, ShareName is replaced by the name of your share (case sensitive) and the quotes are included.

You can either restart Apache from SSH or you can cause FrontView to restart it by making a change in the HTTP/S options of any share (you can always set it back again later).

CAUTION: If you make a mistake, it can cause Apache, and thus Frontview, to not restart properly. If you do not have SSH enabled, you may find yourself in a world of hurt, as a firmware reload will not erase this file.

You might be able to put it in a file that does get reset by a firmware reload, like the end of Virtual.conf, which is handled right before addons. But there are also conditions under which Virtual.conf is overwritten (like creating a new share, I think), so you still might lose it.

Great post Sandshark. I've read this thread a few times and couldnt quite understand why the two methods couldnt be active at the same time. In the end I opted to use the Apache File Manager method which works nicely for me. I do struggle with how easy it seems to get to my files at home versus security but then I keep telling myself that someone would need to know the share name, user and and password to get near my files.

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:

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.