# My fork of ngx\_eval 2011.01.12 released

**URL:** <https://www.ruby-forum.com/t/my-fork-of-ngx-eval-2011-01-12-released/201657>\
**Category:** NGINX\
**Created:** [January 12, 2011, 1:00pm UTC](https://www.ruby-forum.com/t/my-fork-of-ngx-eval-2011-01-12-released/201657 "2011-01-12T13:00:05Z")\
**Posts on this page:** 1\
**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:** [January 12, 2011, 1:00pm UTC](https://www.ruby-forum.com/t/my-fork-of-ngx-eval-2011-01-12-released/201657/1 "2011-01-12T13:00:05Z")

</div>

Hi, folks!

People have been reporting issues of my fork of ngx\_eval when using it  
with recent versions of nginx. I’ve updated it to version 2011.01.12  
to compatible with nginx 0.8.54+:

```
https://github.com/agentzh/nginx-eval-module/downloads

```

Now “eval\_subrequest\_in\_memory” is off by default. Because  
subrequest\_in\_memory mode is still having issues.

Here’s a small example for using ngx\_eval with my ngx\_redis2, an nginx  
upstream module that supports the full Redis 2.0 unified wired  
protocol:

location /foo {  
eval\_override\_content\_type ‘application/octet-stream’;  
eval\_subrequest\_in\_memory off;  
eval $res {  
redis2\_literal\_raw\_query ‘set one 5\r\nfirst\r\n’;  
redis2\_pass 127.0.0.1:6379;  
}  
echo [$res];  
}

Accessing /foo with curl yields

[+OK  
]

on my side.

Please ensure that you’re using nginx 0.8.54+ and the latest version  
of my fork of ngx\_eval (at lease 2010.12.29+ is required).

If you find any issues, please let me know.

Special thanks go to Valery K. for creating ngx\_eval in the first  
place.

Cheers,  
-agentzh

P.S. Still, it’s recommended to use ngx\_lua module’s rewrite\_by\_lua or  
access\_by\_lua directives combined by the “ngx.location.capture” API to  
do what my fork of ngx\_eval has been doing.