# Nginx-1.1.8

**URL:** <https://www.ruby-forum.com/t/nginx-1-1-8/213856>\
**Category:** NGINX\
**Created:** [November 14, 2011, 4:44pm UTC](https://www.ruby-forum.com/t/nginx-1-1-8/213856 "2011-11-14T16:44:27Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![luislavena](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/0ea827/32.png) [@luislavena](https://www.ruby-forum.com/u/luislavena)\
**Post date:** [November 14, 2011, 4:44pm UTC](https://www.ruby-forum.com/t/nginx-1-1-8/213856/1 "2011-11-14T16:44:27Z")

</div>

Changes with nginx 1.1.8 14 Nov  
2011

```
*) Change: the ngx_http_limit_zone_module was renamed to the
   ngx_http_limit_conn_module.

*) Change: the "limit_zone" directive was superseded by the
   "limit_conn_zone" directive with a new syntax.

*) Feature: support for multiple "limit_conn" limits on the same 

```

level.

```
*) Feature: the "image_filter_sharpen" directive.

*) Bugfix: a segmentation fault might occur in a worker process if
   resolver got a big DNS response.
   Thanks to Ben Hawkes.

*) Bugfix: in cache key calculation if internal MD5 implementation 

```

was  
used; the bug had appeared in 1.0.4.

```
*) Bugfix: the "If-Modified-Since", "If-Range", etc. client request
   header lines might be passed to backend while caching; or not 

```

passed  
without caching if caching was enabled in another part of the  
configuration.

```
*) Bugfix: the module ngx_http_mp4_module sent incorrect
   "Content-Length" response header line if the "start" argument was
   used.
   Thanks to Piotr S..

```

–  
Igor S.

---

<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:** [November 25, 2011, 4:04am UTC](https://www.ruby-forum.com/t/nginx-1-1-8/213856/2 "2011-11-25T04:04:44Z")

</div>

2011/11/14 Igor S. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid):

> Changes with nginx 1.1.8 14 Nov 2011
> 
> \*) Change: the ngx\_http\_limit\_zone\_module was renamed to the  
> ngx\_http\_limit\_conn\_module.
> 
> \*) Change: the “limit\_zone” directive was superseded by the  
> “limit\_conn\_zone” directive with a new syntax.
> 
> \*) Feature: support for multiple “limit\_conn” limits on the same level.

Usually we use limit\_zone module like:  
http{

limit\_zone one $binary\_remote\_addr 10m;  
server  
{  
location /mypage{  
limit\_conn one number\_of connections;  
}  
}

What is the scenario that we should use multiple limit\_conn ?

Is there a way to limit total connections to one location ?

---

<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:** [November 25, 2011, 11:01am UTC](https://www.ruby-forum.com/t/nginx-1-1-8/213856/3 "2011-11-25T11:01:10Z")

</div>

Hello!

On Fri, Nov 25, 2011 at 11:03:39AM +0800, Delta Y. wrote:

> > 
> 
> }
> 
> What is the scenario that we should use multiple limit\_conn ?

E.g. if you want to limit number of connections per ip _and_ total  
number of connections per virtual host.

```
limit_conn_zone $binary_remote_addr zone=perip:10m;
limit_conn_zone $server_name zone=perserver:10m;

server {
    ...
    limit_conn perip 10;
    limit_conn perserver 100;
}

```

> Is there a way to limit total connections to one location ?

Yes.

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:** [November 28, 2011, 8:22am UTC](https://www.ruby-forum.com/t/nginx-1-1-8/213856/4 "2011-11-28T08:22:16Z")

</div>

On Fri, Nov 25, 2011 at 02:00:24PM +0400, Maxim D. wrote:

> > > \*) Change: the “limit\_zone” directive was superseded by the  
> > > {  
> > > limit\_conn\_zone $binary\_remote\_addr zone=perip:10m;  
> > > Yes.  
> > > I’ve just updated documentation with this particular example:

> **[Module ngx\_http\_limit\_conn\_module](http://nginx.org/en/docs/http/ngx_http_limit_conn_module.html#limit_conn)**
>
> The ngx\_http\_limit\_conn\_module module is used to limit the number of connections per the defined key, in particular, the number of connections from a single IP address.

---

<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:** [November 25, 2011, 11:51am UTC](https://www.ruby-forum.com/t/nginx-1-1-8/213856/5 "2011-11-25T11:51:39Z")

</div>

So if I want to limit total connection to one uri, I can do it by:

limit\_conn\_zone $host$uri zone=peruri:10m;

```
server {
    ...
    location / {
        limit_conn peruri 10;
  }

}

```

but because uri is

2011/11/25 Maxim D. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid):