> The purpose of is to group things into one logical block. If you
> want things to fail in order without checking other conditions, don’t use
> requireAll?
I am using RequireAll with two conditions.
The first condition is "Require valid user".
For the second one I have an environmental
* typo in the message above. I meant "HTTP 401 instead of HTTP 403".
Additionally,
I looked at the debug log right now. The thing is that if I will put just
Require valid user in the RequireAll section, in the log I would see "denied
(no authentocated user yet)". Yet if I will put "Require env
Is it possible to force apache to return HTTP 401 instead of HTTP if any
condition inside RequireAll fails?
In known about AuthzSendForbiddenOnFailure, but it does opposite of what I need.
-
To unsubscribe, e-mail:
Dude, what are you talking about?
The user's credentials are encoded into the HTTP request header
"Authorization". In my question I showed how one can unencode it and compare
against part of the path at the same HTTP request.
I already figured out how to solve my problem, BTW. I did it with
Good day everyone! I've got a question related to Basic Authorization and Home
directory detection. Namely, I want to configure the webserver in such a way
that it allows to do autoindex if user is browsing their home directory. I
tried to declare an environment variable first, but then
