Forum: NGINX nginx-0.7.21

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
5640e332954fc0006aea97a155ce0afd?d=identicon&s=25 Igor Sysoev (Guest)
on 2008-11-11 21:16
(Received via mailing list)
Changes with nginx 0.7.21                                        11 Nov

    *) 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 Benson and Maxim Dounin.

    *) Bugfix: nginx could not run on MacOSX 10.4 and earlier; the bug
       appeared in 0.7.6.
6ad5db789866d1b72302287aacec01b9?d=identicon&s=25 Thomas (Guest)
on 2008-11-11 21:36
(Received via mailing list)
Simply fantastic!

Thank you Igor and all contributors.
1d7e58690643fef4a92750ff39f4c56c?d=identicon&s=25 Kevin Worthington (Guest)
on 2008-11-11 21:51
(Received via mailing list)
Nginx 0.7.21 for Windows is now available:

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

Kevin Worthington
F5a6ed477b109fe6acc11a5a8f87e7e8?d=identicon&s=25 mike (Guest)
on 2008-11-11 23:51
(Received via mailing list)

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 :)
0d76ff0bea2959efb5f46bb2883b9f1c?d=identicon&s=25 Johan Bergström (Guest)
on 2008-11-12 00:21
(Received via mailing list)

On Nov 11, 2008, at 21:07 , Igor Sysoev 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

> --
> Igor Sysoev

Kind regards,
5640e332954fc0006aea97a155ce0afd?d=identicon&s=25 Igor Sysoev (Guest)
on 2008-11-12 08:30
(Received via mailing list)
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 {
F5a6ed477b109fe6acc11a5a8f87e7e8?d=identicon&s=25 mike (Guest)
on 2008-11-12 10:43
(Received via mailing list)
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
Be2f65409d85d0856e8a66f1019860fe?d=identicon&s=25 Athan Dimoy (Guest)
on 2008-11-12 13:54
(Received via mailing list)
May I ask when (if) these changes will be backported to 6.xx stable

This topic is locked and can not be replied to.