www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From m...@apache.org
Subject Re: config/5170: Cannot configure Apache to log successfull login authorization.
Date Tue, 19 Oct 1999 20:46:55 GMT
[In order for any reply to be added to the PR database, ]
[you need to include <apbugs@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.                                      ]
[Reply only with text; DO NOT SEND ATTACHMENTS!         ]


Synopsis: Cannot configure Apache to log successfull login authorization.

State-Changed-From-To: open-closed
State-Changed-By: marc
State-Changed-When: Tue Oct 19 13:46:53 PDT 1999
State-Changed-Why:
Every time a user gets a restricted document, they "log in".
It is completely in the browser; Apache requires the
authentication for every request.  If it doesn't get it,
it sends a 401 and the browser prompts the user.

However, even if the user has "logged in" the browser can decide
not to send it in a particular situation, or it can decide
to send it just because it thinks it should.

So there is no concept of "logging in" for Apache to
know about since it is entirely a client side operation.


Mime
View raw message