Random order of configuration file reading

Gena Makhomed gmm at csdoc.com
Wed Nov 28 12:55:04 UTC 2012

On 28.11.2012 14:23, Maxim Dounin wrote:

>> This is a known issue. It has been fixed in our own
>> Tengine<http://tengine.taobao.org>
>>   distribution:
>> https://github.com/taobao/tengine/blob/master/src/os/unix/ngx_files.c#L362
>> If you want to use official nginx only, you can apply the patch below:
>> @Maxim:
>> Would you please consider to apply this patch to the trunk? Thanks in
>> advance.
> I've already proposed removing GLOB_NOSORT to Igor a while ago.
> His position on this is to keep this in sync with Windows version
> where there is no sort guaranties.

this just can be described in documentation as drawback
of windows version of nginx, as many other "Known issues"
and limitations at http://nginx.org/en/docs/windows.html

because the UNIX version of nginx is the major and main stream.
so the best possible capabilities must be present in UNIX version,
not in windows one. and windows version must be compatible with
UNIX version, if this is possible.

now - capabilities of mainstream UNIX version artificially limited
to be "compatible" with even not-production-ready windows version.

this is very strange and unexpected and confusing
for users of mainstream UNIX/Linux version of nginx
(and this is more than 99% of all use cases of nginx)

for example, windows 7 not support cache module
and many other modules - but this is not reason
for remove this feature from UNIX version of nginx.


similar example: method java.io.File.renameTo
(function "rename")works differently on Windows and UNIX,
this is "Known issues" and can't be avoided in any case.

btw, similar "rename bugs" and incompatibilities also
must be presented also in windows/unix version of nginx

java.io.File.renameTo has different semantics on Solaris and Win32


Best regards,

More information about the nginx mailing list