Nginx-0.8.37

Server NGINX
1

Changes with nginx 0.8.37 17 May
2010

*) Feature: the ngx_http_split_clients_module.

*) Feature: the "map" directive supports keys more than 255

characters.

*) Bugfix: nginx ignored the "private" and "no-store" values in the
   "Cache-Control" backend response header line.

*) Bugfix: a "stub" parameter of an "include" SSI directive was not
   used, if empty response has 200 status code.

*) Bugfix: if a proxied or FastCGI request was internally redirected

to
another proxied or FastCGI location, then a segmentation fault
might
occur in a worker process; the bug had appeared in 0.8.33.
Thanks to Yichun Z…

*) Bugfix: IMAP connections may hang until they timed out while

talking
to Zimbra server.
Thanks to Alan Batie.

–
Igor S.
http://sysoev.ru/en/

2

Thanks Igor.

Regards,
Joe

3

How to use ngx_http_split_clients_module?
Please give an example.

4

lhmwzy at 2010-5-17 16:51 wrote:

How to use ngx_http_split_clients_module?
Please give an example.

read this:
http://www.ruby-forum.com/topic/209653#new

nginx mailing list
[email protected]
nginx Info Page

–
Weibin Y.

5

On Mon, May 17, 2010 at 04:51:45PM +0800, lhmwzy wrote:

How to use ngx_http_split_clients_module?
Please give an example.

http {
split_clients “${remote_addr}AAA” $variant {
0.5% .one;
2.0% .two;
- “”;
}

server {
    location / {
        index  index${variant}.html;

$cookie_…, etc, may be used as a source for splitting.
The source string is hashed using CRC32 and the percent of the hash
is used as source value.

–
Igor S.
http://sysoev.ru/en/

6

Thanks Igor.

2010/5/17 Igor S. [email protected]

7

Igor S. ha scritto:

Changes with nginx 0.8.37 17 May 2010
[…]
*) Bugfix: nginx ignored the “private” and “no-store” values in the
“Cache-Control” backend response header line.

By the way, last time I checked the code, I noted that Nginx always
ignore the Vary header, and require the cache key to be explicitly set.

Is it possible to have a default cache key, generated from request URI
(including query string) and Vary header?

[…]

Thanks Manlio

8

On Tue, May 18, 2010 at 05:59:07PM +0200, Manlio P. wrote:

Is it possible to have a default cache key, generated from request URI
(including query string) and Vary header?

The Vary header is response header, you can not use it in cache key.

–
Igor S.
http://sysoev.ru/en/

9

Igor S. ha scritto:

Is it possible to have a default cache key, generated from request URI
(including query string) and Vary header?

The Vary header is response header, you can not use it in cache key.

I meant the Vary header from backend response.

Regards Manlio

10

Igor S. ha scritto:

does not know them: the key is used to find a cached backend response.

The idea is two use a two level cache lookup.

The first level is done using original cache_key.
The associated cache zone will contain the Vary header specified when
backend response is cached.

The second level is done using cache_key updated with request headers
specified in Vary header.

This is just an idea, I was curious to know if adding support to Vary
header is possible with current implementation.

Thanks Manlio

11

On Tue, May 18, 2010 at 06:34:18PM +0200, Manlio P. wrote:

ignore the Vary header, and require the cache key to be explicitly set.

Is it possible to have a default cache key, generated from request URI
(including query string) and Vary header?

The Vary header is response header, you can not use it in cache key.

I meant the Vary header from backend response.

Backend response headers can not be used in cache key, because nginx
does not know them: the key is used to find a cached backend response.

–
Igor S.
http://sysoev.ru/en/