My Pleasure, ^_^<br><br>Wating for your fixed version <img goomoji="330" style="margin: 0pt 0.2ex; vertical-align: middle;" src="cid:330@goomoji.gmail"><br><br><div class="gmail_quote">在 2011年3月17日 下午2:44，agentzh <span dir="ltr"><<a href="mailto:agentzh@gmail.com">agentzh@gmail.com</a>></span>写道：<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">On Tue, Mar 15, 2011 at 7:45 PM, Wendal Chen <<a href="mailto:wendal1985@gmail.com">wendal1985@gmail.com</a>> wrote:<br>
><br>
> #用中文再说一遍,英语水平有限:<br>
> 我得到的最小集合就是:<br>
> 1. nginx.conf<br>
> location /test {<br>
> root html;<br>
> content_by_lua_file "conf/test.lua";<br>
> }<br>
> server/http等配置按默认的, event module用的是 epoll<br>
><br>
> 2. test.lua文件仅2行:<br>
> ngx.location.capture('/1.html')<br>
> ngx.exec("/1.html")<br>
><br>
> 我尝试过,无论这两句话是否请求同一个文件,结果都一样.<br>
><br>
> 3. 1.html文件里面仅有几个字母,我已经试过不同的文件大小,结果一样<br>
><br>
><br>
> 我遇到的情况是这样的:<br>
> 1. 通过wget/curl/Firefox来访问 localhost/test 都能正常显示1.html中的内容<br>
> 2. 使用ab访问 localhost/1.html是正常的,能够pass<br>
> 3. 使用ab进行测试,总是timeout ,<br>
<br>
</div>I've reproduced it on my side. This is indeed a bug. When ngx.exec()<br>
is used after ngx.location.capture() or ngx.location.capture_multi(),<br>
nginx 0.8.11+ will not close the client connection due to leaked<br>
request reference counter (r->main->count). A hacky work-around is to<br>
disable nginx http keepalive and rely on the browser (and other http<br>
clients) to actively close the connection. And that's why wget, curl,<br>
firefox, and other well-written http clients worked for you.<br>
<br>
Nginx 0.7.68 (and older) is confirmed to work in this context just<br>
because older nginx does not use reference counting.<br>
<br>
I'll attempt fix in the next few days. Thank you for reporting this<br>
and sorry about this issue :)<br>
<br>
Cheers,<br>
<font color="#888888">-agentzh<br>
</font></blockquote></div><br>