Thanks Daniel for the reply.
I have attached my config file for reference in a previous reply.
On Wed, Jan 25, 2023 at 10:58 AM nanaya wrote:
> Just adding, if it's `location /auth {}`, it'll also match /autha, /authb,
> /authsomething/something, not just limited to /auth/*.
>
> On Wed, Jan 25,
I have attached my config file which may help to understand it better. With
this change, I am getting "404 - Not Found" error and in log it says
[error] 11#11: *49 access forbidden by rule, client: 10.48.11.9, server: _,
request: "GET /auth/ HTTP/1.1", host: "my.domain.info", referrer: "
https://
Just adding, if it's `location /auth {}`, it'll also match /autha, /authb,
/authsomething/something, not just limited to /auth/*.
On Wed, Jan 25, 2023, at 01:56, Reinis Rozitis wrote:
>> There are other locations like /auth, /auth/, /auth/admin, /auth/admin/ and
>> few more which have the same r
> There are other locations like /auth, /auth/, /auth/admin, /auth/admin/ and
> few more which have the same rules. I am trying to restrict access to /auth
> and /auth/admin which are sensitive for public access. Do you think removing
> "=" can help in this case?
'=' in location definition me
