# Nginx-0.7.59

**URL:** <https://www.ruby-forum.com/t/nginx-0-7-59/168756>\
**Category:** NGINX\
**Created:** [May 25, 2009, 1:44pm UTC](https://www.ruby-forum.com/t/nginx-0-7-59/168756 "2009-05-25T13:44:11Z")\
**Posts on this page:** 17\
**Page:** 1

<div class="post-metadata">

**Author:** ![imixaly4](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/3ab097/32.png) [@imixaly4](https://www.ruby-forum.com/u/imixaly4)\
**Post date:** [May 25, 2009, 1:44pm UTC](https://www.ruby-forum.com/t/nginx-0-7-59/168756/1 "2009-05-25T13:44:11Z")

</div>

Changes with nginx 0.7.59 25 May  
2009

```
*) Feature: the "proxy_cache_methods" and "fastcgi_cache_methods"
   directives.

*) Bugfix: socket leak; the bug had appeared in 0.7.25.
   Thanks to Maxim D..

*) Bugfix: a segmentation fault occurred in worker process,
   if a request had no body and the $request_body variable was used;
   the bug had appeared in 0.7.58.

*) Bugfix: the SSL modules might not built on Solaris and Linux;
   the bug had appeared in 0.7.58.

*) Bugfix: ngx_http_xslt_filter_module responses were not handled by
   SSI, charset, and gzip filters.

*) Bugfix: a "charset" directive did not set a charset to
   ngx_http_gzip_static_module responses.

```

The 0.7.x version status is changed to stable.  
While 0.7.x version development the following features appreared:

```
*) caching of proxied and FastCGI servers;
*) "try_files" directive;
*) the "location" and "server_name" directives support captures
   in regular expressions;
*) XLST and image filters;
*) a preliminary IPv6 support;
*) nginx/Windows.
```

---

<div class="post-metadata">

**Author:** ![imixaly4](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/3ab097/32.png) [@imixaly4](https://www.ruby-forum.com/u/imixaly4)\
**Post date:** [May 25, 2009, 2:43pm UTC](https://www.ruby-forum.com/t/nginx-0-7-59/168756/2 "2009-05-25T14:43:28Z")

</div>

Congratulations on reaching the 0.7.x stable milestone. Thanks again  
for your continuing efforts to make Nginx an outstanding web server.

Cheers

Dave

---

<div class="post-metadata">

**Author:** ![imixaly4](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/3ab097/32.png) [@imixaly4](https://www.ruby-forum.com/u/imixaly4)\
**Post date:** [May 25, 2009, 3:06pm UTC](https://www.ruby-forum.com/t/nginx-0-7-59/168756/3 "2009-05-25T15:06:20Z")

</div>

Great news! Thank u for the hard works.  
What’s your plan for 0.8.x ?

2009/5/25 Igor S. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)

---

<div class="post-metadata">

**Author:** ![imixaly4](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/3ab097/32.png) [@imixaly4](https://www.ruby-forum.com/u/imixaly4)\
**Post date:** [May 25, 2009, 8:17pm UTC](https://www.ruby-forum.com/t/nginx-0-7-59/168756/4 "2009-05-25T20:17:27Z")

</div>

Hi Igor,

> -----Original Message-----  
> From: Igor S. [[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)]  
> Posted At: Monday, May 25, 2009 7:28 AM  
> Posted To: gmane.comp.web.nginx.english  
> Conversation: nginx-0.7.59  
> Subject: nginx-0.7.59
> 
> Changes with nginx 0.7.59 25  
> May  
> 2009
> 
> ```
> *) Feature: the "proxy_cache_methods" and "fastcgi_cache_methods"
> directives.
> 
> ```

I cannot find into Russian documentation an example of those directives.  
Thanks for posting a link.

Floren

---

<div class="post-metadata">

**Author:** ![imixaly4](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/3ab097/32.png) [@imixaly4](https://www.ruby-forum.com/u/imixaly4)\
**Post date:** [May 25, 2009, 8:38pm UTC](https://www.ruby-forum.com/t/nginx-0-7-59/168756/5 "2009-05-25T20:38:38Z")

</div>

On Mon, May 25, 2009 at 02:08:50PM -0400, Floren M. wrote:

> May
> 
> > 2009
> > 
> > ```
> > *) Feature: the "proxy_cache_methods" and "fastcgi_cache_methods"
> > directives.
> > 
> > ```
> 
> I cannot find into Russian documentation an example of those directives.  
> Thanks for posting a link.

There is still no Russian documentation of these directives.  
These directives allows to cache POST methods.

Syntax:  
proxy\_cache\_methods [GET HEAD POST];

Default:  
proxy\_cache\_methods GET HEAD;

GET/HEAD is syntax sugar, i.e. you can not disable GET/HEAD even  
if you set just

proxy\_cache\_methods POST;

---

<div class="post-metadata">

**Author:** ![imixaly4](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/3ab097/32.png) [@imixaly4](https://www.ruby-forum.com/u/imixaly4)\
**Post date:** [May 25, 2009, 9:54pm UTC](https://www.ruby-forum.com/t/nginx-0-7-59/168756/6 "2009-05-25T21:54:26Z")

</div>

Hi Igor,

> Syntax:  
> proxy\_cache\_methods [GET HEAD POST];
> 
> Default:  
> proxy\_cache\_methods GET HEAD;
> 
> GET/HEAD is syntax sugar, i.e. you can not disable GET/HEAD even  
> if you set just
> 
> proxy\_cache\_methods POST;

Thanks for the info.

Regards,

Floren M.  
Axivo Inc.

---

<div class="post-metadata">

**Author:** ![imixaly4](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/3ab097/32.png) [@imixaly4](https://www.ruby-forum.com/u/imixaly4)\
**Post date:** [May 26, 2009, 11:15am UTC](https://www.ruby-forum.com/t/nginx-0-7-59/168756/7 "2009-05-26T11:15:40Z")

</div>

Hey,

Could you say something more about the socket leak? When exactly does it  
occur?

Regards,

Mike

---

<div class="post-metadata">

**Author:** ![imixaly4](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/3ab097/32.png) [@imixaly4](https://www.ruby-forum.com/u/imixaly4)\
**Post date:** [May 26, 2009, 12:05pm UTC](https://www.ruby-forum.com/t/nginx-0-7-59/168756/8 "2009-05-26T12:05:30Z")

</div>

On Mon, May 25, 2009 at 05:18:25PM -0500, Resicow wrote:

> Hi Igor,
> 
> Currently I am using proxy\_cache, but have a question on how nginx  
> handles range requests for a file that is not currently in cache. Will  
> nginx simply proxy the file and not cache it, or download the entire  
> file into cache, but just serve the range request to the client.

nginx gets the entire file and returns the range to the client.  
There is issue with multiple ranges in one request (although this is  
rare case, as I know only Acrobat Reader does such requests).  
For the first request when response would be cached, nginx is able  
to serve only first range of the request. But with already cached  
response  
nginx is able to serve all ranges of the request.

---

<div class="post-metadata">

**Author:** ![imixaly4](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/3ab097/32.png) [@imixaly4](https://www.ruby-forum.com/u/imixaly4)\
**Post date:** [May 26, 2009, 12:25am UTC](https://www.ruby-forum.com/t/nginx-0-7-59/168756/9 "2009-05-26T00:25:10Z")

</div>

Hi Igor,

Currently I am using proxy\_cache, but have a question on how nginx  
handles range requests for a file that is not currently in cache. Will  
nginx simply proxy the file and not cache it, or download the entire  
file into cache, but just serve the range request to the client.

Congrats on 0.7.59, and keep up the great work!

Thanks,

John

---

<div class="post-metadata">

**Author:** ![imixaly4](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/3ab097/32.png) [@imixaly4](https://www.ruby-forum.com/u/imixaly4)\
**Post date:** [May 26, 2009, 12:07pm UTC](https://www.ruby-forum.com/t/nginx-0-7-59/168756/10 "2009-05-26T12:07:17Z")

</div>

Hello!

On Tue, May 26, 2009 at 11:05:58AM +0200, Michał Jaszczyk wrote:

> Hey,
> 
> Could you say something more about the socket leak? When exactly does it occur?

Here description of patch I’ve posted a while ago (on russian  
mailing list, but there was at least link in english list as well):

[cut here]  
Fix connection leak under some specific conditions.

Return code of ngx\_http\_output\_filter() wasn’t correctly checked in  
ngx\_http\_writer() function. This resulted in incorrect processing of  
connections closed prematurely by clients - these connections were  
sometimes  
closed due to timeouts (and hence higher numbers of ‘Writing’  
connections  
were observed in stub\_status module compared to previous versions), and  
sometimes permanently leaked.

Since the issue is racy it’s hard to reproduce it without accept filters  
used. Though it’s relatively easy too with

```
listen ... accept_filter=httpready;
sendfile_max_chunk 16k;

```

by requesting big file and closing client connection immediately.

The bug had appeared in 0.7.25.  
[cut here]

I belive it can be also reproduced with limit\_rate used, but I’ve  
never checked.

Maxim D.

---

<div class="post-metadata">

**Author:** ![imixaly4](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/3ab097/32.png) [@imixaly4](https://www.ruby-forum.com/u/imixaly4)\
**Post date:** [May 26, 2009, 2:30pm UTC](https://www.ruby-forum.com/t/nginx-0-7-59/168756/11 "2009-05-26T14:30:57Z")

</div>

Igor S. wrote:

> ```
> the bug had appeared in 0.7.58.
> 
> ```

Hi Igor,

Congrats for the stable status.  
Does it mean this version will make its way into Debian stable (lenny)  
repositories soon ?  
Or is this the maintener’s (Jose Parrella & Fabio Tranchitella) choice ?

---

<div class="post-metadata">

**Author:** ![imixaly4](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/3ab097/32.png) [@imixaly4](https://www.ruby-forum.com/u/imixaly4)\
**Post date:** [May 26, 2009, 12:10pm UTC](https://www.ruby-forum.com/t/nginx-0-7-59/168756/12 "2009-05-26T12:10:14Z")

</div>

On Tue, May 26, 2009 at 11:05:58AM +0200, Micha?? Jaszczyk wrote:

> Hey,
> 
> Could you say something more about the socket leak? When exactly does it occur?

See English comment in  
[http://article.gmane.org/gmane.comp.web.nginx.russian/24085](http://article.gmane.org/gmane.comp.web.nginx.russian/24085)

---

<div class="post-metadata">

**Author:** ![imixaly4](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/3ab097/32.png) [@imixaly4](https://www.ruby-forum.com/u/imixaly4)\
**Post date:** [May 26, 2009, 4:43pm UTC](https://www.ruby-forum.com/t/nginx-0-7-59/168756/13 "2009-05-26T16:43:51Z")

</div>

El Tue, May 26, 2009 at 02:20:23PM +0200, Michael Baudino va escriure:

> Congrats for the stable status.  
> Does it mean this version will make its way into Debian stable (lenny)  
> repositories soon ?  
> Or is this the maintener’s (Jose Parrella & Fabio Tranchitella) choice ?

Unless something really strange happens it will never go into the  
official  
Debian Lenny repositories.

On stable Debian releases packages are only updated for security or  
grave  
functionality bugs and the norm is to update the package version  
backporting  
the changes (i.e. if the Lenny nginx package is 0.6.32-3 and a security  
bug is  
found and fixed on upstream version 0.6.38 the debian security update  
will be  
based on upstream 0.6.32 with the security fix taken from the upstream  
0.6.38  
version, but without the rest of changes done upstream).

The idea behind this policy is that stable means stable and there should  
not  
be ABI, API or functionality changes on stable Debian releases if  
possible to  
avoid new bugs and/or regressions.

Anyway that does not mean that you can’t install newer version of nginx  
on  
Debian Lenny, it just means that you have to do extra work and know what  
you  
are doing.

If you don’t plan to maintain your own packages the most common option  
is to  
use [http://backports.org/](http://backports.org/), a service run by Debian Developers that  
provides  
newer versions of some packages recompiled for the stable distribution.

As for nginx, you can see the list of available nginx packages on:

[Debian -- Package Search Results -- nginx](http://packages.debian.org/nginx)

If you want to have the latest version the way to go is:

- report a wishlist bug asking the maintainers to upload the new version  
to  
unstable if there is none,

- once the package is available on testing/unstable ask someone to  
upload it  
to backports (the official maintainers are a good option, as they only  
need  
to recompile and upload their own package)

Probably it seems that you need to do a lot of things, but the truth is  
that  
a lot of times when you want updates of server programs like nginx you  
find  
them on backports without doing anything… but you can always help to  
make it  
happen faster… 😉

Greetings,

Sergio.

---

<div class="post-metadata">

**Author:** ![imixaly4](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/3ab097/32.png) [@imixaly4](https://www.ruby-forum.com/u/imixaly4)\
**Post date:** [May 26, 2009, 2:52pm UTC](https://www.ruby-forum.com/t/nginx-0-7-59/168756/14 "2009-05-26T14:52:10Z")

</div>

On Tue, May 26, 2009 at 02:20:23PM +0200, Michael Baudino wrote:

> > ```
> > if a request had no body and the $request_body variable was used;
> > 
> > *) nginx/Windows.
> > 
> > ```
> 
> Hi Igor,
> 
> Congrats for the stable status.  
> Does it mean this version will make its way into Debian stable (lenny)  
> repositories soon ?  
> Or is this the maintener’s (Jose Parrella & Fabio Tranchitella) choice ?

This is maintener’s choice.

---

<div class="post-metadata">

**Author:** ![imixaly4](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/3ab097/32.png) [@imixaly4](https://www.ruby-forum.com/u/imixaly4)\
**Post date:** [May 28, 2009, 12:01am UTC](https://www.ruby-forum.com/t/nginx-0-7-59/168756/15 "2009-05-28T00:01:45Z")

</div>

## Wicked Wrote:

> Hello,
> 
> its my first time with nginx, but i love this  
> small fast and great webserver… big respect to  
> you igor… 🙂
> 
> but i have a question how i upgrade to the new  
> version?.. i have a debian lenny…
> 
> thanks in advance  
> …configure/make/make install …haha.

Posted at Nginx Forum:

> **[Re: nginx-0.7.59](https://forum.nginx.org/read.php?2,2335,2413#msg-2413)**
>
> Changes with nginx 0.7.59 25 May 2009 \*) Feature: the "proxy\_cache\_methods" and "fastcgi\_cache\_methods" directives. \*) Bugfix: socket leak; the bug had appeared in 0.7.25. Th

---

<div class="post-metadata">

**Author:** ![imixaly4](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/3ab097/32.png) [@imixaly4](https://www.ruby-forum.com/u/imixaly4)\
**Post date:** [May 27, 2009, 5:02pm UTC](https://www.ruby-forum.com/t/nginx-0-7-59/168756/16 "2009-05-27T17:02:48Z")

</div>

Hello,

its my first time with nginx, but i love this small fast and great  
webserver… big respect to you igor… 🙂

but i have a question how i upgrade to the new version?.. i have a  
debian lenny…

thanks in advance

Posted at Nginx Forum:

> **[Re: nginx-0.7.59](https://forum.nginx.org/read.php?2,2335,2407#msg-2407)**
>
> Changes with nginx 0.7.59 25 May 2009 \*) Feature: the "proxy\_cache\_methods" and "fastcgi\_cache\_methods" directives. \*) Bugfix: socket leak; the bug had appeared in 0.7.25. Th

---

<div class="post-metadata">

**Author:** ![imixaly4](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/3ab097/32.png) [@imixaly4](https://www.ruby-forum.com/u/imixaly4)\
**Post date:** [May 28, 2009, 2:24pm UTC](https://www.ruby-forum.com/t/nginx-0-7-59/168756/17 "2009-05-28T14:24:57Z")

</div>

Ok thanks 😛

Posted at Nginx Forum:

> **[Re: nginx-0.7.59](https://forum.nginx.org/read.php?2,2335,2434#msg-2434)**
>
> Changes with nginx 0.7.59 25 May 2009 \*) Feature: the "proxy\_cache\_methods" and "fastcgi\_cache\_methods" directives. \*) Bugfix: socket leak; the bug had appeared in 0.7.25. Th