It seems like if I protect pages, my site works fine. But when I do just that, it doesn't protect all of the files on that page (I could still copy and paste the link to a file in the address bar and it would load like normal). If I protect just a few files, it seems to work...but when I do all of them that I want protected, it doesn't.

Some pages I have, I want to protect some files and not others...I was under the impression WAM could do this by picking and choosing the files. But when I select all of the files I want protected, I end up getting:



If I remove WAM, go back to protecting just a page, and reupload, it will protect the pages immediately (so there doesn't seem to be a lag in the server recognizing the .htaccess) - but I still run into the problem of the files not being protected when I type the direct link to them in. lunarpages is the server host.

I had tried creating a separate folder for just the files I want protected so I could just protect the folder, but I got the same error codes.

I had submitted a support ticket, but the day after everything was working fine (after a WAM removal and re-upload)...so nothing was investigated further. I will likely go back and resubmit if I can't get it working correctly again. I tried waiting and doing the same thing this time, and it's still not working (when I have all the files selected that I want protected).

I'm not sure what the problem is, but I'm getting a little frustrated that this is happening every time I'm trying to update the protections. I don't mind troubleshooting it, but this isn't a personal page and I'm trying to make it as simple as possible for whomever takes over for me in about a year or so.

It does that when you browser cache's. Once you access the protected pages your browser saves your spot until you cancel out of your browser.

I should clarify...I hadn't accessed the protected pages. I didn't actually fill in the password at any point. I hit cancel, and then I typed in the link to a different page, and it loaded (though it should have been protected).

that also doesn't explain why when I protect individual files, it gives me the server error...If I protect one file, it seems to work just fine. it's when I add multiple files (while leaving others unprotected as there are some documents I want open to the public) that the problem arises.

right now what is happening is when I click on one of the pages I protected, it'll prompt me with the password prompt. But even when I fill it in, access it, and click on documents that are on the server I get the error code posted in the original post.

If I remove WAM, unclick all of the individual files I want protected, choose one or two files only (as well as the pages), then it will work as desired....but that doesn't help in the long run as it leaves many files I need unprotected.

Have you tried to protect a directory instead of individual files?

I tried moving the files I want protected to a different folder and protecting just that folder (along with the 2 pages), and I got the same results I am getting now.

I don't want to protect the entire download folder as there are files in there that I do want open, although I supposed that could be a route I can go if it can't be fixed any other way. The files I am trying to protect are ones that have personal information in them - those that don't have personal informtion, I'd like to remain open.

I believe WAM can do this, I'm just not sure what's going wrong in the process. 2 days ago everything was working fine. I added a new page yesterday with new files, and protected those files the same way i had the previous ones, and when I uploaded the changes I started getting the internal server error.

It sounds like you configured something incorrectly if you are getting that error. I would need to see the hdb file to figure out what the problem is. Adding a new page should definitely not cause any problems.

I've added the HDB file in my support ticket as of just a few minutes ago...shall I add it here?

No. That. Would give the world access to your server.

lol, yes that would be bad