Hi Valentin, On Wednesday 30 January 2013 22:54:29 Valentin V. Bartenev wrote: > I would prefer something like "autoindex_sort" directive > > autoindex_sort criterion [ order ]; > > with variables support. > > And if user want Apache-like behavior then he will be able to configure > it like this: > > map $arg_C $criteria { > default nameby Lekensteyn - Nginx Development
On Wednesday 30 January 2013 22:54:29 Valentin V. Bartenev wrote: > I would prefer something like "autoindex_sort" directive > > autoindex_sort criterion [ order ]; > > with variables support. > > And if user want Apache-like behavior then he will be able to configure > it like this: > > map $arg_C $criteria { > default name; > Mby Lekensteyn - Nginx Development
Hi, Thank you for your feedback. On Wednesday 30 January 2013 21:50:57 Maxim Dounin wrote: > Overrall I tend to think that it's bad idea to do autoindex more > customizable. I would rather like to see it producing XML and > hence any customization being possible with XSLT filter. Do you want nginx to spit out XML? I am in favor of passing parameters this way to nginx so that the clby Lekensteyn - Nginx Development
Based on Apache HTTPD autoindex docs[1]. Supported: - C=N sorts the directory by file name - C=M sorts the directory by last-modified date, then file name - C=S sorts the directory by size, then file name - O=A sorts the listing in Ascending Order - O=D sorts the listing in Descending Order Not supported (does not make sense for nginx): - C=D sorts the directory by description, then file name - Aby Lekensteyn - Nginx Development
A preliminary patch for (1) sorting can be found on http://lekensteyn.nl/files/nginx/Autoindex-support-sorting-using-URL-parameters.patch "preliminary" because no headers are added, you can use URL params though.by Lekensteyn - Ideas and Feature Requests
I consider it a feature if try_files and if can really check whether a file exists or not (instead of accessible). I have cooked a patch [1] that implements this functionality. Please review, comments are welcome. Note: this patch changes behaviour. Previously, files which were not accessible were simply skipped. After applying this patch, files which exist, but are not accessible are not skippby Lekensteyn - Nginx Mailing List - English
Maxim, I found that the disable_symlinks option does not work properly when the permissions are restrictive. Please see my observations on http://serverfault.com/q/463243/51929. In summary: ngx_file_info_wrapper() tries to open() a file if symlinks are disabled. That fails if nginx does not have read permissions for the said file.by Lekensteyn - Nginx Mailing List - English