[openresty] openresty中capture_multi如何与upstream结合使用？

jzj.jackie · 2012-05-04T16:50:50+00:00

2012/5/4 huang kun <ku...@gmail.com>: > 测的时候第一次发现mysql中select userID,password...

[openresty] openresty中capture_multi如何与upstream结合使用？

jzj.jackie

Hi agentzh;

我想把前端的请求经由nginx多路转发给后台的apache以及tomcat服务器，然后对后台服务器返回的数据做一些归并和排序处理。在实验的时
候，遇到了如下问题，

2012/05/04 16:09:57 [error] 1195#0: *1 connect() failed (111:
Connection refused) while connecting to upstream, client:
61.135.152.195, server: localhost, request: "GE\
T /multi HTTP/1.1", subrequest: "/s1", upstream: "http://
127.0.0.1:10001/s1", host: "XXXXX.XXXX.XXXX.XXXX:10000"

请问，为何请求是发给http://127.0.0.1:10001/s1，而不是http://127.0.0.1:10001呢？;

谢谢啦！

下面是nginx.conf配置。

worker_processes  1;
error_log logs/error.log;

events {
    worker_connections 51200;
}

http {
upstream cluster_1 { //apache servers
  server localhost:10001;
}

upstream cluster_2 { //tomcat servers
  server localhost:10002;
}


server {
    listen       10000;
    server_name  localhost;

    location /multi {
      proxy_pass_request_headers off;

      content_by_lua '
        local res1, res2 = ngx.location.capture_multi{
          { "/s1" },
          { "/s2" },
        }

        ngx.say(res1.status);
        if res1.status == ngx.HTTP_OK then
          ngx.print(res1.body);
        end
      ';
    }

   location /s2 {
      proxy_pass http://cluster_2;
    }

  }
}

defage

应该要在location /s1里面写个rewrite把，另外配置里似乎没有location /s1的配置，不知道回答的对不对，错了请无视请无视.

2012/5/4 JackieJIANG <jzj....@gmail.com>

Hi agentzh;

我想把前端的请求经由nginx多路转发给后台的apache以及tomcat服务器，然后对后台服务器返回的数据做一些归并和排序处理。在实验的时
候，遇到了如下问题，

2012/05/04 16:09:57 [error] 1195#0: *1 connect() failed (111:
Connection refused) while connecting to upstream, client:
61.135.152.195, server: localhost, request: "GE\
T /multi HTTP/1.1", subrequest: "/s1", upstream: "http://
127.0.0.1:10001/s1", host: "XXXXX.XXXX.XXXX.XXXX:10000"

请问，为何请求是发给http://127.0.0.1:10001/s1，而不是http://127.0.0.1:10001呢？

谢谢啦！

下面是nginx.conf配置。

worker_processes 1;
error_log logs/error.log;

events {
worker_connections 51200;
}

http {
upstream cluster_1 { //apache servers
server localhost:10001;
}

upstream cluster_2 { //tomcat servers
server localhost:10002;
}

server {
listen 10000;
server_name localhost;

location /multi {
proxy_pass_request_headers off;

content_by_lua '
local res1, res2 = ngx.location.capture_multi{
{ "/s1" },
{ "/s2" },
}

ngx.say(res1.status);
if res1.status == ngx.HTTP_OK then
ngx.print(res1.body);
end
';
}

location /s2 {
proxy_pass http://cluster_2;
}

}
}

--
刘太华

jzj.jackie

呵呵，谢谢太华。我试试rewrite吧！

s1的配置忘记粘贴了 :-(
 location /s1 {
      proxy_pass http://cluster_1;
    }



On 5月4日, 下午4时57分, 刘太华 <def...@gmail.com> wrote:
> 应该要在location  /s1里面写个rewrite把，另外配置里似乎没有location /s1的配置，不知道回答的对不对，错了请无视请无视.
>
> 2012/5/4 JackieJIANG <jzj.jac...@gmail.com>
>
>
>
>
>
>
>
>
>
> > Hi agentzh;
>
> > 我想把前端的请求经由nginx多路转发给后台的apache以及tomcat服务器，然后对后台服务器返回的数据做一些归并和排序处理。在实验的时
> > 候，遇到了如下问题，
>
> > 2012/05/04 16:09:57 [error] 1195#0: *1 connect() failed (111:
> > Connection refused) while connecting to upstream, client:
> > 61.135.152.195, server: localhost, request: "GE\
> > T /multi HTTP/1.1", subrequest: "/s1", upstream: "http://
> > 127.0.0.1:10001/s1", host: "XXXXX.XXXX.XXXX.XXXX:10000"
>
> > 请问，为何请求是发给http://127.0.0.1:10001/s1，而不是http://127.0.0.1:10001呢？;
>
> > 谢谢啦！
>
> > 下面是nginx.conf配置。
>
> > worker_processes  1;
> > error_log logs/error.log;
>
> > events {
> >    worker_connections 51200;
> > }
>
> > http {
> > upstream cluster_1 { //apache servers
> >  server localhost:10001;
> > }
>
> > upstream cluster_2 { //tomcat servers
> >  server localhost:10002;
> > }
>
> > server {
> >    listen       10000;
> >    server_name  localhost;
>
> >    location /multi {
> >      proxy_pass_request_headers off;
>
> >      content_by_lua '
> >        local res1, res2 = ngx.location.capture_multi{
> >          { "/s1" },
> >          { "/s2" },
> >        }
>
> >        ngx.say(res1.status);
> >        if res1.status == ngx.HTTP_OK then
> >          ngx.print(res1.body);
> >        end
> >      ';
> >    }
>
> >   location /s2 {
> >      proxy_passhttp://cluster_2;
> >    }
>
> >  }
> > }
>
> > --
> 刘太华

jzj.jackie

looks it works for me now. thanks man. :-)

2012/5/4 JackieJIANG <jzj....@gmail.com>

呵呵，谢谢太华。我试试rewrite吧！

s1的配置忘记粘贴了 :-(
location /s1 {
proxy_pass http://cluster_1;

}

On 5月4日, 下午4时57分, 刘太华 <def...@gmail.com> wrote:
> 应该要在location /s1里面写个rewrite把，另外配置里似乎没有location /s1的配置，不知道回答的对不对，错了请无视请无视.
>

> 2012/5/4 JackieJIANG <jzj.jac...@gmail.com>

>
>
>
>
>
>
>
>
>
> > Hi agentzh;
>
> > 我想把前端的请求经由nginx多路转发给后台的apache以及tomcat服务器，然后对后台服务器返回的数据做一些归并和排序处理。在实验的时
> > 候，遇到了如下问题，
>
> > 2012/05/04 16:09:57 [error] 1195#0: *1 connect() failed (111:
> > Connection refused) while connecting to upstream, client:
> > 61.135.152.195, server: localhost, request: "GE\
> > T /multi HTTP/1.1", subrequest: "/s1", upstream: "http://
> > 127.0.0.1:10001/s1", host: "XXXXX.XXXX.XXXX.XXXX:10000"
>
> > 请问，为何请求是发给http://127.0.0.1:10001/s1，而不是http://127.0.0.1:10001呢？
>
> > 谢谢啦！
>
> > 下面是nginx.conf配置。
>
> > worker_processes 1;
> > error_log logs/error.log;
>
> > events {
> > worker_connections 51200;
> > }
>
> > http {
> > upstream cluster_1 { //apache servers
> > server localhost:10001;
> > }
>
> > upstream cluster_2 { //tomcat servers
> > server localhost:10002;
> > }
>
> > server {
> > listen 10000;
> > server_name localhost;
>
> > location /multi {
> > proxy_pass_request_headers off;
>
> > content_by_lua '
> > local res1, res2 = ngx.location.capture_multi{
> > { "/s1" },
> > { "/s2" },
> > }
>
> > ngx.say(res1.status);
> > if res1.status == ngx.HTTP_OK then
> > ngx.print(res1.body);
> > end
> > ';
> > }
>
> > location /s2 {

> > proxy_passhttp://cluster_2;

> > }
>
> > }
> > }
>
> >
> --
> 刘太华

--
Jackie

jzj.jackie

在cluster_1后面加“/” 就好了。哪位大神解释一下是什么原理呢？:-)

from :

location /s1 {

proxy_pass http://cluster_1;

}

to:

location /s1 {

proxy_pass http://cluster_1/;

}

2012/5/4 蒋子俊 <jzj....@gmail.com>

looks it works for me now. thanks man. :-)

2012/5/4 JackieJIANG <jzj....@gmail.com>

呵呵，谢谢太华。我试试rewrite吧！

s1的配置忘记粘贴了 :-(
location /s1 {
proxy_pass http://cluster_1;

}

On 5月4日, 下午4时57分, 刘太华 <def...@gmail.com> wrote:
> 应该要在location /s1里面写个rewrite把，另外配置里似乎没有location /s1的配置，不知道回答的对不对，错了请无视请无视.
>

> 2012/5/4 JackieJIANG <jzj.jac...@gmail.com>

>
>
>
>
>
>
>
>
>
> > Hi agentzh;
>
> > 我想把前端的请求经由nginx多路转发给后台的apache以及tomcat服务器，然后对后台服务器返回的数据做一些归并和排序处理。在实验的时
> > 候，遇到了如下问题，
>
> > 2012/05/04 16:09:57 [error] 1195#0: *1 connect() failed (111:
> > Connection refused) while connecting to upstream, client:
> > 61.135.152.195, server: localhost, request: "GE\
> > T /multi HTTP/1.1", subrequest: "/s1", upstream: "http://
> > 127.0.0.1:10001/s1", host: "XXXXX.XXXX.XXXX.XXXX:10000"
>
> > 请问，为何请求是发给http://127.0.0.1:10001/s1，而不是http://127.0.0.1:10001呢？
>
> > 谢谢啦！
>
> > 下面是nginx.conf配置。
>
> > worker_processes 1;
> > error_log logs/error.log;
>
> > events {
> > worker_connections 51200;
> > }
>
> > http {
> > upstream cluster_1 { //apache servers
> > server localhost:10001;
> > }
>
> > upstream cluster_2 { //tomcat servers
> > server localhost:10002;
> > }
>
> > server {
> > listen 10000;
> > server_name localhost;
>
> > location /multi {
> > proxy_pass_request_headers off;
>
> > content_by_lua '
> > local res1, res2 = ngx.location.capture_multi{
> > { "/s1" },
> > { "/s2" },
> > }
>
> > ngx.say(res1.status);
> > if res1.status == ngx.HTTP_OK then
> > ngx.print(res1.body);
> > end
> > ';
> > }
>
> > location /s2 {

> > proxy_passhttp://cluster_2;

> > }
>
> > }
> > }
>
> >
> --
> 刘太华

--
Jackie

agentzh

2012/5/4 蒋子俊 <jzj....@gmail.com>:
> 在cluster_1后面加"/"  就好了。哪位大神解释一下是什么原理呢？:-)
>

在 ngx_proxy 模块的文档中已经解释过了：

"If it is necessary to transmit URI in the unprocessed form then
directive proxy_pass should be used without URI part:

    location  /some/path/ {
      proxy_pass   http://127.0.0.1;
    }
"

所以，当你不期望把当前 nginx 请求的 URI 转递给远方 http 服务的话，则需要自己加上 URI part，则那个尾随的 /
部分，否则当前请求的 URI 也会被代理到后面，即请求 http://127.0.0.1:10001/s1 这样的东西。

Best regards,
-agentzh

jzj.jackie

谢谢春哥。:-)

2012/5/4 agentzh <age...@gmail.com>

2012/5/4 蒋子俊 <jzj....@gmail.com>:

> 在cluster_1后面加"/" 就好了。哪位大神解释一下是什么原理呢？:-)
>

在 ngx_proxy 模块的文档中已经解释过了：

"If it is necessary to transmit URI in the unprocessed form then
directive proxy_pass should be used without URI part:

location /some/path/ {
proxy_pass http://127.0.0.1;
}
"

所以，当你不期望把当前 nginx 请求的 URI 转递给远方 http 服务的话，则需要自己加上 URI part，则那个尾随的 /
部分，否则当前请求的 URI 也会被代理到后面，即请求 http://127.0.0.1:10001/s1 这样的东西。

Best regards,
-agentzh

--
Jackie