> 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
On Oct 2, 2019, at 5:53 PM, Jack Simmons wrote:
> Is it possible to force apache to return HTTP 401 instead of HTTP [403] if
> any condition inside RequireAll fails?
The two codes mean different things.
401 basically means “hey, you need to login or login again” (Unauthorized)
while 403 means
* 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:
