Re: [users@httpd] Confusing (incorrect?) documentation for AuthzProviderAlias

2022-12-03 Thread Eric Covener
On Sat, Dec 3, 2022 at 5:13 PM sebb wrote: > > On Sat, 3 Dec 2022 at 20:39, Eric Covener wrote: > > Thanks for the speedy reply. > > > > > On Sat, Dec 3, 2022 at 3:21 PM sebb wrote: > > > > > > The documentation for AuthzProviderAlias [1] looks wrong. > > > > > > AFAICT including 'Require all gr

Re: [users@httpd] Confusing (incorrect?) documentation for AuthzProviderAlias

2022-12-03 Thread sebb
On Sat, 3 Dec 2022 at 20:39, Eric Covener wrote: Thanks for the speedy reply. > > On Sat, Dec 3, 2022 at 3:21 PM sebb wrote: > > > > The documentation for AuthzProviderAlias [1] looks wrong. > > > > AFAICT including 'Require all granted' means that anyone can access > > the directory. > > This

Re: [users@httpd] Confusing (incorrect?) documentation for AuthzProviderAlias

2022-12-03 Thread Eric Covener
On Sat, Dec 3, 2022 at 3:21 PM sebb wrote: > > The documentation for AuthzProviderAlias [1] looks wrong. > > AFAICT including 'Require all granted' means that anyone can access > the directory. > This is borne out by my local testing. That is odd and should not be in the example, even in such a c

[users@httpd] Confusing (incorrect?) documentation for AuthzProviderAlias

2022-12-03 Thread sebb
The documentation for AuthzProviderAlias [1] looks wrong. AFAICT including 'Require all granted' means that anyone can access the directory. This is borne out by my local testing. If I remove the Require line, then httpd complains "AuthUserFile not specified in the configuration". Presumably this