Dear Mr Francis, issue 1.) > That is almost certainly because you also have "proxy_cache" ( http://nginx.org/r/proxy_cache) and "proxy_cache_path" defined, but configured to use part of the filesystem that the nginx user - is not allowed to use -- maybe it was created or first run as one user, and now this user cannot write there? > The simplest-to-understand fix,by amiladevops - Nginx Mailing List - English
Hi Francis, Hope you are doing good ? Thanks for your quick responses for my emails again. I have 02 questions for you today, I will brief it down for your ease. *quiz (1.) : * Yes I understand some of my clients requests don't have user/name password in their requests and that's why it gives 401 in the access.log file. But also for me when I browse the site in my internal network brby amiladevops - Nginx Mailing List - English
_______________________________________________ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginxby amiladevops - Nginx Mailing List - English
Hi Francis, Thanks for your reply email, here are my findings and progress and current situation about my issue. First of all I will answer your questions and then you will have a better idea to guide me and whether I'm on the correct path. >As I understand it, the load balancer is making the request "OPTIONS /" >to nginx, and nginx is responding with a http 405, and you don't wby amiladevops - Nginx Mailing List - English
_______________________________________________ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginxby amiladevops - Nginx Mailing List - English