Step 4: Creating folders and define access If you have to create more users, you should either use the command line tool or use a script.įinally, my htpasswd file looks as follows:įor testing purposes, the password for each user is ‘test’. Each user is assigned a password. For testing purposes, you can use this tool to generate several passwords for your users. Let’s say I’ve got five different users: each user is assigned a unique number. htaccess file will be accepted by the web server in my directories! Step 3: Creating users and passwords You may find more detailled information here. Note that there is a separate switch Indexes only. Let’s say I want to enable indexes, my directory tag could look like this – AllowOverride is set to All: conf in the directory /private/etc/apache2/users which overrules the settings from the nf!). This setting usually resides in the nf file of the web server (note: on OS X systems there is a separate file called. The next step is to tell the Apache web server that Indexing should be allowed for a certain directory. The only thing that is VITAL is that the htpasswd file is not accessible to the general public (usually it is not).
This time the idea is to create a download server for many customers – where each customer would need to receive individual files (imagine you providing 50 customers with 50 different PDF files).
These who are technical aware will use a proper program to access the data (and thus won’t care for beauty), but those who do not know how to use such a tool will be prompted with something like that:Ī real beauty, isn’t she? We can do much better than that.
What if you do not possess a beautiful CMS system such as WordPress? Of course, you could just set up a FTP server and provide your customers with login credentials. Sometimes you are required to deliver data to your customers.