# Nginx-0.6.18

**URL:** <https://www.ruby-forum.com/t/nginx-0-6-18/121401>\
**Category:** NGINX\
**Created:** [November 27, 2007, 5:32pm UTC](https://www.ruby-forum.com/t/nginx-0-6-18/121401 "2007-11-27T17:32:14Z")\
**Posts on this page:** 6\
**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:** [November 27, 2007, 5:32pm UTC](https://www.ruby-forum.com/t/nginx-0-6-18/121401/1 "2007-11-27T17:32:14Z")

</div>

Changes with nginx 0.6.18 27 Nov  
2007

```
*) Change: now the ngx_http_userid_module adds start time 

```

microseconds  
to the cookie field contains a pid value.

```
*) Change: now the full request line instead of URI only is written 

```

to  
error\_log.

```
*) Feature: variables support in the "proxy_pass" directive.

*) Feature: the "resolver" and "resolver_timeout" directives.

*) Feature: now the directive "add_header last-modified ''" deletes 

```

a  
“Last-Modified” response header line.

```
*) Bugfix: the "limit_rate" directive did not allow to use full
   throughput, even if limit value was very high.
```

---

<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 29, 2007, 7:21pm UTC](https://www.ruby-forum.com/t/nginx-0-6-18/121401/2 "2007-11-29T19:21:21Z")

</div>

On Tue, 2007-11-27 at 19:25 +0300, Igor S. wrote:

> Changes with nginx 0.6.18 27 Nov 2007

> ```
> *) Feature: variables support in the "proxy_pass" directive.
> 
> ```

I somehow missed this feature. Outstanding!

Cliff

---

<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 30, 2007, 5:06am UTC](https://www.ruby-forum.com/t/nginx-0-6-18/121401/3 "2007-11-30T05:06:51Z")

</div>

On Tue, 2007-11-27 at 19:25 +0300, Igor S. wrote:

> Changes with nginx 0.6.18 27 Nov 2007

> ```
> *) Feature: variables support in the "proxy_pass" directive.
> 
> ```

Any chance variable support will make it into fastcgi\_pass and upstream  
directives soon as well?

Regards,  
Cliff

---

<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 30, 2007, 8:27am UTC](https://www.ruby-forum.com/t/nginx-0-6-18/121401/4 "2007-11-30T08:27:17Z")

</div>

On Thu, Nov 29, 2007 at 07:52:51PM -0800, Cliff W. wrote:

> On Tue, 2007-11-27 at 19:25 +0300, Igor S. wrote:
> 
> > Changes with nginx 0.6.18 27 Nov 2007
> 
> > ```
> > *) Feature: variables support in the "proxy_pass" directive.
> > 
> > ```
> 
> Any chance variable support will make it into fastcgi\_pass and upstream  
> directives soon as well?

fastcgi\_pass will support variables.  
How do see you variables in upstream ?

---

<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 30, 2007, 11:16pm UTC](https://www.ruby-forum.com/t/nginx-0-6-18/121401/5 "2007-11-30T23:16:34Z")

</div>

On Fri, 2007-11-30 at 09:44 +0300, Igor S. wrote:

> fastcgi\_pass will support variables.  
> That will be great.

> How do see you variables in upstream ?

I’m mostly interested in managing a large number of backends (shared  
hosting environment) where each client gets an internal IP address  
(127.0.0.0). Using map makes it quite simple to prevent collisions  
(assigning same internal IP to two different clients).

Mostly I am interested in _never_ putting an actual IP address in the  
server section, only in the map section.

map $host $internal\_ip {  
hostnames;  
.host1.com 127.0.0.2;  
.host2.com 127.0.0.3;  
.host3.com 127.0.0.3;  
}

upstream cluster {  
$internal\_ip:8000;  
$internal\_ip:8001;  
$internal\_ip:8002;  
$internal\_ip:8003;  
}

server {  
server\_name [www.host1.com](http://www.host1.com);  
location / {  
proxy\_pass [http://cluster](http://cluster);  
}  
}

server {  
server\_name [www.host2.com](http://www.host2.com);  
location / {  
proxy\_pass [http://cluster](http://cluster);  
}  
}

Regards,  
Cliff

---

<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 30, 2007, 11:25pm UTC](https://www.ruby-forum.com/t/nginx-0-6-18/121401/6 "2007-11-30T23:25:20Z")

</div>

On Fri, 2007-11-30 at 14:07 -0800, Cliff W. wrote:

> map $host $internal\_ip {  
> hostnames;  
> .host1.com 127.0.0.2;  
> .host2.com 127.0.0.3;  
> .host3.com 127.0.0.3;  
> }

And of course I meant

map $host $internal\_ip {  
hostnames;  
.host1.com 127.0.0.2;  
.host2.com 127.0.0.3;  
.host3.com 127.0.0.4;  
}

Cliff