atom feed9 messages in ru.sysoev.nginxRe: http_auth_request_module Instruct...
FromSent OnAttachments
Nginx UserSep 3, 2011 2:01 pm 
Maxim DouninSep 3, 2011 3:24 pm 
Nginx UserSep 4, 2011 9:40 am 
Maxim DouninSep 4, 2011 11:00 am 
Nginx UserSep 4, 2011 12:07 pm 
Andrey N. OktyabrskiSep 4, 2011 12:32 pm 
Nginx UserSep 4, 2011 12:49 pm 
Maxim DouninSep 4, 2011 3:00 pm 
Nginx UserSep 4, 2011 3:35 pm 
Subject:Re: http_auth_request_module Instructions?
From:Nginx User (ngi@nginxuser.net)
Date:Sep 4, 2011 3:35:32 pm
List:ru.sysoev.nginx

On Mon, Sep 5, 2011 at 1:01 AM, Maxim Dounin <mdou@mdounin.ru> wrote:

Hello!

On Sun, Sep 04, 2011 at 10:08:30PM +0300, Nginx User wrote:

[...]

Last query on this.

The information on the "satisfy" directive in the wiki states that:

* all - Both Access *and* Auth Basic directives must grant access to the context * any - Either Access *or* Auth Basic directives grant access to the context Is this miss leading? Should it be something like:

* all - All access phase handlers must grant access to the context * any - Any access phase handler can grant access to the context

Both versions are right, though first one implicitly assumes you are using only standard access modules.

I'll say the first set is technically wrong as it *implies* the directive only applies to those two modules. The key is in the use of the words "both" and "either" which imply a sum total of two possibilities.

I edited the wiki to read:

Access policy if directives from multiple access phase handlers, such as the Access and Auth Basic modules, are defined in a context: * all - All access phase handlers must grant access to the context * any - Any access phase handler can grant access to the context

Thanks!

_______________________________________________ nginx mailing list ngi@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx