Sorry for taking so long; I had to put that server into production. So I built another (the first one is an ubuntu one), applied your patch to nginx-0.8.50 (it did not bark), and compiled it. So, I set the conf dir as location /conf { hidden; } and restarted nginx. Unfortunately I can still see the directory. Did I miss anything?by raubvogel - Nginx Mailing List - English
I would really appreciate if you could update this patch; it sure sounds like exactly what I need. Thanks!by raubvogel - Nginx Mailing List - English
Thanks for the suggestion. Unfortunately the directory conf is still being shown. Once I click on it, I get the 404 error. Here is the conf file for the site, just in case I have done something somewhere else that is affecting this (nginx.conf has not being touched): server { listen 80 default; # Default site server_name _; autoindex on; access_log /var/log/nginx/packages-errorby raubvogel - Nginx Mailing List - English
Let's say I have a directory named conf in the root of my website I want to hide. From what I understood, if I have location /conf { deny all; } It will not allow anybody to see what is inside /conf. But, what if I do not want people even to know that /conf is there to begin with, while other files and directories are visible?by raubvogel - Nginx Mailing List - English