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://my.domain.info"; It seems that the rule is working but at some wrong place, I am not sure how to organise or set the right sequence here. On Tue, Jan 24, 2023 at 10:26 PM Reinis Rozitis <r...@roze.lv> wrote: > > 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 means that nginx will use it only on exact uri > match. > > if you have location = /auth {} but client requests /auth/admin (unless > you have also location = /auth/admin) then that particular location > configuration won't be used and will match the 'location / {}' which in > your configuration sample was proxied without any deny rules. > > By removing the '=' it means all the /auth, /auth/* requests will be > processed in that location. > > Good to also check the documentation on it > http://nginx.org/en/docs/http/ngx_http_core_module.html#location > > rr > _______________________________________________ > nginx mailing list > nginx@nginx.org > https://mailman.nginx.org/mailman/listinfo/nginx > -- Regards, Sandeep
ngxinx.conf
Description: Binary data
_______________________________________________ nginx mailing list nginx@nginx.org https://mailman.nginx.org/mailman/listinfo/nginx
