Nginx-0.7.21


#1

Changes with nginx 0.7.21 11 Nov
2008

*) Changes in the ngx_http_limit_req_module.

*) Feature: the EXSLT support in the ngx_http_xslt_module.
   Thanks to Denis F. Latypoff.

*) Workaround: compatibility with glibc 2.3.
   Thanks to Eric B. and Maxim D..

*) Bugfix: nginx could not run on MacOSX 10.4 and earlier; the bug 

had
appeared in 0.7.6.


#2

Simply fantastic!

Thank you Igor and all contributors.


#3

Nginx 0.7.21 for Windows is now available:
http://cli.gs/n4w0721

Please provide feedback if you use this Windows port of Nginx.

Thanks,
Kevin

Kevin W.


#4

Cool!

Question -

Is there any way nginx can support conditional error logging and
conditional debugging?

Turning on debugging for an entire server produces way too much
output. I’d love to be able to turn on debugging anywhere. From server
{} or location {} or even an if statement. This was one thing that
lighttpd was great with.

Same with error logging - there are a couple conditions where I’d like
to turn error_log off - but error_log is a global setting.

These two things would make my life a bit easier. Especially the
debugging one. I have the misfortune of supporting a complex site
setup with a ton of rewrites and a handful of location blocks and
such, and it helps to be able to debug which one(s) are being
triggered, but each HTTP request produces like 50-60 lines of output -
and one page might trigger 10-20 HTTP requests easily. That’s a lot of
scroll and text to deal with …

Thanks :slight_smile:


#5

Hey,

On Nov 11, 2008, at 21:07 , Igor S. wrote:

*) Bugfix: nginx could not run on MacOSX 10.4 and earlier; the
bug had
appeared in 0.7.6.

Just a thought - but how about doing -RC’s (or some kind of SCM -
please don’t turn this thread into a bike-shed about SCM tho) and
setting up a simple buildbot system that us users can connect to? This
would further enhance the quality of these releases.

I for one have a couple of hosts that i could add to this rotation,
and perhaps other users have some less used operating systems to
submit.


Igor S.
http://sysoev.ru/en/

Kind regards,
Johan
Bergström


#6

Oh! Cool! I must have missed debug_connection. I will have to try that
out. Also I think the wiki says error_log is only in global scope not
server


#7

On Tue, Nov 11, 2008 at 02:42:53PM -0800, mike wrote:

lighttpd was great with.
scroll and text to deal with …
You may set error_log per server or location, but not inside “if”.
As to a debugging error_log, I have found that is more convenient
to set it per IP-address:

error_log /path/to/log notice;

events {
debug_connection 192.168.1.0/24;
debug_connection 192.168.10.1;
}


#8

May I ask when (if) these changes will be backported to 6.xx stable
branch?

Thanks,
Athan