DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24901>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24901

User authentication error causes a 500 Internal Server Error

           Summary: User authentication error causes a 500 Internal Server
                    Error
           Product: Apache httpd-1.3
           Version: 1.3.29
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Auth/Access
        AssignedTo: [email protected]
        ReportedBy: [EMAIL PROTECTED]


Under the document root directory description, I have placed the following in 
my 
httpd.conf file...all modules are in the distribution are enabled and 
uncommented....basically not much change from the standard released httpd.conf 
file in the Apache Group Windows Binary Distribution.

<Directory "D:/Program Files/Apache Group/Apache/htdocs">
    Options Indexes FollowSymLinks MultiView
    AllowOverride None
        AuthName TESTING11
        AuthType Basic
        AuthAuthoritative Off
        AuthUserFile "D:/Program Files/Apache Group/Apache/conf/passwd"
        require valid-user
</Directory>

There is one active and valid user in the passwd file.

I enter http://myhost.com

and correctly get the authentication box.  I enter NOTHING and press the OK box.
I get a "500 Internal Server Configuration Error" and the error.log shows the 
message:

[Fri Nov 21 10:03:35 2003] [crit] [client 1.2.3.4] configuration error:  
couldn't check user.  No user file?: /

After that until the BROWSER is restarted, any page access gets the 500 error.

However, in the case of starting up the browser via http://myhost.com and when 
getting the authentication request, I enter the right and correct information...
.all is ok.

Also, entering the Wrong information in the authentication request causes the 
same 500 configuration error.

I have looked through the bug reports and documentation but do not find this 
situation covered and looks like a bug to me.

M. D. Parker
[EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to