I am an extreme Newbie to both Linux and Apache.

I am running Redhat 7.3 and Apache 1.3.28 and FrontPage Extension Version4.0.

I am trying to learn about setting up passwords for individual directories. I have read through the Apache manual several times and searched multiple sites for this problem. It seems other posts only have trouble gaining authorization.

I am currently testing apache using our intranet. I have been able to serve the web page fine but cannot get any machine local or another client respond to any password settings I have tried.



I have tried setting up Authorization types Digest and Basic. Both with and without using the .htacces files.

I would like to set it up from my httpd.conf within Directory directives.

Here is the section from my httpd.conf regarding the auth files. I have tried putting this section both inside and outside of the <VirtualHost. When Apache starts up it says that it is using the 192.xxx.x.xxx for the ServerName, Syntax OK. so I thought I should put it within the VirtualHost section.

I will e-mail you the complete httpd.conf apon request.

<VirtualHost 192.xxx.x.xxx>
<Directory /var/www/html/xxx/0708>
AllowOverride None
AuthType Digest
AuthName "Password and Id Required"
AuthDigestFile /usr/local/xxxx/xxx/.htpasswd
require user kxinc
Satisfy all
</Directory>
</VirtualHost>


Thanks in advance, I am running out of things to try and am beginning to think it is something having todo with another control outside of Apache. BTW I have turned off ipchaines and iptables.

just in case you see something new:

http://wsabstract.com/howto/htaccess3.shtml
http://www.isrl.uiuc.edu/systems/Doc...ess_howto.html
http://www.dsm.fordham.edu/~moniot/C...ess-howto.html

Thanks for the links.

I tried to duplicate the settings in one of the links just for fun. I still cannot get my browser to respond to the .htaccess commands.

Do any commands/methods exist to debug where the problem is occurring with the .htaccess? Someone said on another post to type junk into the .htaccess file. I tried this and still get all the same responses.

Here is a link I just found for others having a similar problem. This helped me to realize my problem could be beyound the apache set-up.

http://apache-server.com/tutorials/A...-htaccess.html

Here is the troubleshooting section from this link.

Troubleshooting
Here are some of the most common problems I've seen people have (or have had myself) with .htaccess files. One thing I should stress first, though: the server error log is your friend. You should always consult the error log when things don't seem to be functioning correctly. If it doesn't say anything about your problem, try boosting the message detail by changing your LogLevel directive to debug. (Or adding a LogLevel debug line of you don't have a LogLevel already).

'Internal Server Error' page is displayed when a document is requested
This indicates a problem with your configuration. Check the Apache error log file for a more detailed explanation of what went wrong. You probably have used a directive that isn't allowed in .htaccess files, or have a directive with incorrect syntax.
.htaccess file doesn't seem to change anything
It's possible that the directory is within the scope of an AllowOverride None directive. Try putting a line of gibberish in the .htaccess file and force a reload of the page. If you still get the same page instead of an 'Internal Server Error' display, then this is probably the cause of the problem. Another slight possibility is that the document you're requesting isn't actually controlled by the .htaccess file you're editing; this can sometimes happen if you're accessing a document with a common name, such as index.html. If there's any chance of this, try changing the actual document and requesting it again to make sure you can see the change. this isn't happening.
I've added some security directives to my .htaccess file, but I'm not getting challenged for a username and password
The most common cause of this is having the .htaccess directives within the scope of a Satisfy Any directive. Explicitly disable this by adding a