Bug in nginx?

Hi,

I’m still using Nginx 0.7.67 and I think I have found a minor bug.

In my config files, for one domain I have entries like this to protect
two directories.

location /secret {
index index.html
auth_basic “Please login”;
auth_basic_user_file /path/to/passwordfile
}

location /private {
auth_basic “Hello, Please login”;
authObasic_user_file /path/to/passwordfile;
if ()
etc

Note the second line above has no trailing semi-colon.

The result is that /secret is not protected (although /private is).

The bug is that when nginx is restarted, it announces that the config
file
is valid, when it isn’t, (so the problem was not detected for many
months).

Regards

Ian

Hello!

On Sun, Apr 17, 2011 at 06:26:56PM +0100, Ian H. wrote:

Hi,

I’m still using Nginx 0.7.67 and I think I have found a minor bug.

In my config files, for one domain I have entries like this to
protect two directories.

location /secret {
index index.html
auth_basic “Please login”;

This syntactically correct and defines three possible index files:
“index.html”, “auth_basic” and “Please login”.

auth_basic_user_file /path/to/passwordfile

Note this doesn’t have “;” as well and will make config
syntactially incorrect. You won’t be able to start nginx such
config, but I assume this is artifact introduced during writing
this message.

The result is that /secret is not protected (although /private is).

The bug is that when nginx is restarted, it announces that the config file
is valid, when it isn’t, (so the problem was not detected for many months).

The problem is that config file is actually valid. It’s not
really possible to detect such configuration errors as long as
resulting construct is valid.

Maxim D.

On 17/04/2011 19:12, Maxim D. wrote:

location /secret {
index index.html
auth_basic “Please login”;
This syntactically correct and defines three possible index files:
“index.html”, “auth_basic” and “Please login”.

Hi Maxim,

Your right about that, and the typo later.

Thanks for replying.

Ian

Ok, but who cares? It’s 1.0 active now.

On 4/17/2011 9:26 PM, Ian H. wrote:

Hi,

I’m still using Nginx 0.7.67 and I think I have found a minor bug.


Regards, Vitaly T.
System A.
U.S. +1 (206) 905-9939
Russia +7 911 094-2035

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs