# Nginx-1.2.6 **URL:** \ **Category:** NGINX\ **Created:** [December 11, 2012, 4:01pm UTC](https://www.ruby-forum.com/t/nginx-1-2-6/226510 "2012-12-11T16:01:58Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Maxim\_D](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/da6949/32.png) [@Maxim\_D](https://www.ruby-forum.com/u/Maxim_D)\ **Post date:** [December 11, 2012, 4:01pm UTC](https://www.ruby-forum.com/t/nginx-1-2-6/226510/1 "2012-12-11T16:01:58Z")
Changes with nginx 1.2.6 11 Dec 2012 ``` *) Feature: the $request_time and $msec variables can now be used ``` not only in the “log\_format” directive. ``` *) Bugfix: cache manager and cache loader processes might not be ``` able to start if more than 512 listen sockets were used. ``` *) Bugfix: in the ngx_http_dav_module. ``` – Maxim D. > **[Technical Support for NGINX and NGINX Plus Software](https://www.nginx.com/support/)** > > Get the help you need with support directly from the authors and maintainers of NGINX Open Source and NGINX Plus. ---
**Author:** ![Maxim\_D](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/da6949/32.png) [@Maxim\_D](https://www.ruby-forum.com/u/Maxim_D)\ **Post date:** [December 11, 2012, 4:09pm UTC](https://www.ruby-forum.com/t/nginx-1-2-6/226510/2 "2012-12-11T16:09:33Z")
> ``` > *) Bugfix: in the ngx_http_dav_module. > > ``` Maxim can you be a bit more detailed on this one (using dav module so interested if affected)? rr ---
**Author:** ![Maxim\_D](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/da6949/32.png) [@Maxim\_D](https://www.ruby-forum.com/u/Maxim_D)\ **Post date:** [December 11, 2012, 5:41pm UTC](https://www.ruby-forum.com/t/nginx-1-2-6/226510/3 "2012-12-11T17:41:20Z")
Hello! On Tue, Dec 11, 2012 at 05:08:52PM +0200, Reinis R. wrote: > > \*) Bugfix: in the ngx\_http\_dav\_module. > > Maxim can you be a bit more detailed on this one (using dav module > so interested if affected)? [http://trac.nginx.org/nginx/changeset/4955/nginx](http://trac.nginx.org/nginx/changeset/4955/nginx) – Maxim D. > **[F5 NGINX: Built for cloud-native apps. Ready for AI traffic.](https://www.f5.com/products/nginx)** > > Deliver modern applications with NGINX. Explore high-performance load balancing, API gateways, and web server solutions trusted by top global enterprises. ---
**Author:** ![Maxim\_D](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/da6949/32.png) [@Maxim\_D](https://www.ruby-forum.com/u/Maxim_D)\ **Post date:** [December 11, 2012, 5:46pm UTC](https://www.ruby-forum.com/t/nginx-1-2-6/226510/4 "2012-12-11T17:46:36Z")
> [http://trac.nginx.org/nginx/changeset/4955/nginx](http://trac.nginx.org/nginx/changeset/4955/nginx) Thx. p.s. using on a fuse filesystem - have never encountered something like that rr ---
**Author:** ![Maxim\_D](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/da6949/32.png) [@Maxim\_D](https://www.ruby-forum.com/u/Maxim_D)\ **Post date:** [December 11, 2012, 5:45pm UTC](https://www.ruby-forum.com/t/nginx-1-2-6/226510/5 "2012-12-11T17:45:25Z")
On 11 December 2012 15:01, Maxim D. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > Changes with nginx 1.2.6 11 Dec 2012 > > ``` > *) Feature: the $request_time and $msec variables can now be used not > only in the "log_format" directive. > > ``` This is great! Could you give some examples of other variables that these can now be considered similar to, with respect to when and where they’re available for use? ## Jonathan Jonathan M. // Oxford, London, UK > **[Jonathan Matthews :: Words Typed, Great Rates For Cash](https://www.jpluscplusm.com)** ---
**Author:** ![Maxim\_D](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/da6949/32.png) [@Maxim\_D](https://www.ruby-forum.com/u/Maxim_D)\ **Post date:** [December 11, 2012, 6:14pm UTC](https://www.ruby-forum.com/t/nginx-1-2-6/226510/6 "2012-12-11T18:14:04Z")
Hello! On Tue, Dec 11, 2012 at 06:46:14PM +0200, Reinis R. wrote: > > [http://trac.nginx.org/nginx/changeset/4955/nginx](http://trac.nginx.org/nginx/changeset/4955/nginx) > > Thx. > > p.s. using on a fuse filesystem - have never encountered something like that This is not about filesystem, but rather about configuration. Configuring nginx to handle webdav PUT requests e.g. after error\_page fallback from another proxied location resulted in segmentation fault rather than 500 (Internal Server Error) being returned due to unsupported configuration. – Maxim D. > **[F5 NGINX: Built for cloud-native apps. Ready for AI traffic.](https://www.f5.com/products/nginx)** > > Deliver modern applications with NGINX. Explore high-performance load balancing, API gateways, and web server solutions trusted by top global enterprises. ---
**Author:** ![Maxim\_D](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/da6949/32.png) [@Maxim\_D](https://www.ruby-forum.com/u/Maxim_D)\ **Post date:** [December 11, 2012, 7:33pm UTC](https://www.ruby-forum.com/t/nginx-1-2-6/226510/7 "2012-12-11T19:33:32Z")
Hello! On Tue, Dec 11, 2012 at 04:44:52PM +0000, Jonathan M. wrote: > On 11 December 2012 15:01, Maxim D. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > > > Changes with nginx 1.2.6 11 Dec 2012 > > > > ``` > > *) Feature: the $request_time and $msec variables can now be used not > > only in the "log_format" directive. > > > > ``` > > This is great! Could you give some examples of other variables that > these can now be considered similar to, with respect to when and where > they’re available for use? There are some (semi-)variables which were only available in the log\_format directive, see here for a full list: > **[Module ngx\_http\_log\_module](http://nginx.org/en/docs/http/ngx_http_log_module.html#log_format)** > > The ngx\_http\_log\_module module writes request logs in the specified format. These variables wasn’t available as generic ones as they weren’t expected to be usable during request processing. For now this aproach is reconsidered, and the plan is to eventually make all such variables generic, even if they don’t make much sense till request processing is complete. This will allow, in particular, to use such variables in other modules similar to ngx\_http\_log\_module, or to log some derivative variables using map{}. Semantic of such variables didn’t change when they are made available as generic variables as long as they are used in the “log\_format” directive, i.e. evaluated during request logging. If you’ll try to use them at other phases of a request processing, in some cases previous definitions no longer apply or slightly changes. E.g. $msec, previously defined as (quote from [Module ngx\_http\_log\_module](http://nginx.org/r/log_format)): ``` time in seconds with a milliseconds resolution at the time of log write ``` now defined as (quote from [Module ngx\_http\_core\_module](http://nginx.org/en/docs/http/ngx_http_core_module.html#var_msec)): ``` current time in seconds with a milliseconds resolution ``` Where “current” means a time of the variable evaluation. E.g. if you’ll use it in proxy\_set\_header directive, it will be the time when request to an upstream was created. The $request\_time was defined as (quote from [Module ngx\_http\_log\_module](http://nginx.org/r/log_format)): ``` request processing time in seconds with a milliseconds resolution; time elapsed between the first bytes were read from the client and the log write after the last bytes were sent to the client ``` It remains the same when used in log format, but more generic definition is now available (quote from [Module ngx\_http\_core\_module](http://nginx.org/en/docs/http/ngx_http_core_module.html#var_request_time)): ``` request processing time in seconds with a milliseconds resolution (1.3.9, 1.2.6); time elapsed since the first bytes were read from the client ``` Much like $msec, if you’ll use it in proxy\_set\_header, it will be the time from a request start till nginx created a request to an upstream. And if used in add\_header, it will be the time from a request start till sending response headers to a client. Hope this helps. – Maxim D. > **[F5 NGINX: Built for cloud-native apps. Ready for AI traffic.](https://www.f5.com/products/nginx)** > > Deliver modern applications with NGINX. Explore high-performance load balancing, API gateways, and web server solutions trusted by top global enterprises. ---
**Author:** ![Maxim\_D](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/da6949/32.png) [@Maxim\_D](https://www.ruby-forum.com/u/Maxim_D)\ **Post date:** [December 12, 2012, 1:30pm UTC](https://www.ruby-forum.com/t/nginx-1-2-6/226510/8 "2012-12-12T13:30:56Z")
Hello Nginx U.s, Now available: Nginx 1.2.6 For Windows [http://goo.gl/FMg4H](http://goo.gl/FMg4H) (32-bit and 64-bit versions) These versions are to support legacy users who are already using Cygwin based builds of Nginx. Officially supported native Windows binaries are at [nginx.org](http://nginx.org). Announcements are also available via my Twitter stream ( [http://twitter.com/kworthington](http://twitter.com/kworthington)), if you prefer to receive updates that way. ## Thank you, Kevin Kevin W. kworthington _@_ (gmail] [dot} {com) > **[Kevin Worthington](https://kevinworthington.com/)** > > Practical Tech Guides, Troubleshooting, and Insights on the Modern Internet [http://twitter.com/kworthington](http://twitter.com/kworthington)