Problems with 2.9.0

[GoogleCodeExporter]

1. The access_control_list example +192.168/24 given in the manual creates no 
listener but does generate an error message in the error log. That is,

access_control_list +192.168/24

fails.

There are some problems with the generated error message

[1283706979] [error] [client 0.0.0.0] line 3353: subnet must be [+|-]x.x.x.x[/x]

1.1 The number 1283706979 is presumably the time in Unix seconds. Should be 
converted to localtime or GMT.

1.2 "client 0.0.0.0" doesn't seem to mean anything. There is no such client.

1.3 "line 3353" doesn't seem to mean anything. I don't think even the source 
files are that long.

1.4 "subnet must be [+|-]x.x.x.x[/x]" doesn't match the manual.

2. Each of the following fails to generate a listener AND does NOT generate an 
error message:

access_control_list -0.0.0.0/0,+127.0.0.1
access_control_list -0.0.0.0/0,+127.1.1.1
access_control_list -0.0.0.0/0,+192.168.0.0/16
access_control_list -0.0.0.0/0,+192.168.1.0/24
access_control_list -0.0.0.0/0

3. To show that sometimes mongoose access control works, each of the following 
succeeds in creating a listener with proper access:

#access_control_list
access_control_list +0.0.0.0/0

4. When browsing to localhost to show the root directory listing, the following 
error is logged:

[1283705069] [error] [client 127.1.1.1] GET /favicon.ico: Error 404: Not Found

That might be technically correct, but since looking for favicon is implemented 
in mongoose, I should think that failure to find should be ignored. I'm too 
lazy to test this in Apache.

Note that this time the client is reported correctly (it's one of the valid 
loopback addresses)

5. The installation installs unnecessary files, and deletes all files, even 
those the user has created or modified, including mongoose.conf. I have added a 
warning section to the Windows mongoose wiki with a detailed workaround.

6. With the Windows Service version, there appears to be no way to specify 
mongoose.exe command line options. This means that the config file cannot be 
renamed, as it can with the standalone version.

I apologize if I've got any of the details wrong, but I've already spent a few 
hours on this and need to move on.

Original issue reported on code.google.com by googl...@springtimesoftware.com on 5 Sep 2010 at 5:29

[GoogleCodeExporter]

Sorry, the default Status and Owner of new issues is set incorrectly.

Original comment by googl...@springtimesoftware.com on 5 Sep 2010 at 5:31

• Changed state: New

[GoogleCodeExporter]

These problems (or worse) seem to be happening in standalone 2.9 also.

I get the following error message with no detailed explanation about what I'm 
doing wrong:

"Loading config file D:\Web\Server\mongoose.conf
Cannot initialize Mongoose context"

Attached is the mongoose.conf file with no edits since the error happened.

Original comment by googl...@springtimesoftware.com on 10 Sep 2010 at 5:17

• Added labels: Priority-Critical, Usability
• Removed labels: Priority-High

Attachments:

• mongoose.conf

[GoogleCodeExporter]

The command-line option example in the manual

-l -0.0.0.0/0,+10.0.0.0/8,+1.2.3.4

also seems to fail.

Pardon me for asking, but do you do any testing before you release? I suggest 
creating a testing suite, so you can add a new test whenever there is a new 
feature, and you can be sure there is no error. This is called Regression 
Testing, and it is usually standard in software development. Such a testing 
suite is easy in Linux shell language (I've done it in original Bourne shell to 
test a commercial Fortran compiler with hundreds of tests of four different 
execution types), and just a little harder in Windows.

Hope this helps.

Original comment by googl...@springtimesoftware.com on 10 Sep 2010 at 6:53

[GoogleCodeExporter]

Issue 168 has been merged into this issue.

Original comment by valenok on 12 Sep 2010 at 9:29

[GoogleCodeExporter]

The access_control_list bug is addressed, and 2.10 is released.
Closing this bug.
For poor error message formatting  please open a separate bug. I'll fix it soon.

Original comment by valenok on 12 Sep 2010 at 9:32

• Changed state: Fixed