First a little background. I just upgraded to new dedicated servers using Windows 2003 Server 64 bit. Websites operated under Apache for Windows. I used aMember 3 on the previous servers with a similar setup except that Windows 2003 Server was the 32 bit version. I "converted" my previous aMember MySQL database using aMember's "admin-import3" utility program. I am now trying to use aMember version 4. Everything seems to function properly except one very important thing. When a folder is protected using htaccess you cannot log in. I have tried numerous variations to test logging into the htaccess protected folder. I used the username/password as imported from the old database. I tried changing the password on that member. I created a completely new account. None of these attempts worked. Here is the htaccess file created in the folder: ########### AMEMBER START ##################### AuthType Basic AuthName "Members Only" AuthUserFile C:\Inetpub\wwwroot\amember/data/.htpasswd AuthGroupFile C:\Inetpub\wwwroot\amember/data/.htgroup Require group FOLDER_10 ########### AMEMBER FINISH #################### Any help you can provide is greatly appreciated. Thank you. Larry Carhartt http://www.masterdata.com
After some experimenting, I have found a solution, but hope CGI-Central can modify their code somewhere down the line. The issue apparently is that the protected folders are in sub domains of the primary aMember registered domain. When trying to log in using the sub-domain name which is below the directory structure of the primary domain, log in using either new-rewrite or htaccess does not work. If I use the full path using the primary domain everything works. In other words, http://www.masteremail.com/masterdatacsv/DataUS/ works, but using the sub-domain URL of http://www.masterdatacsv.com/DataUS/ does not even though both point to the same location. Actually the download software uses the IP address of the website for downloads which actually points to the primary domain name. I have clients which have DNS issues from time to time and doing it this way eliminated DNS problems. Anyway, replacing the domain name with the static IP address does not work. I hope that CGI-Central will consider allowing use of a static IP address alternatively to the primary domain name. I understand they may feel they are better protected by not allowing sub-domain names to be used. In any event, I have a solution for now. If anyone has a better way, I would love to hear it. Thank you. Larry Carhartt http://www.masterdata.com
Well, I am sorry. Thefollowup reply by me to the original post is simply wrong. I thought this worked, but no such luck on more intensive subsequent testing. Sorry for the confusion In any event, the issue remains. I cannot log in to an htaccess protected folder Thank you. Larry Carhartt