nginx1.4.7 ip_hash load balancing strategy

[gaoping at richinfo.cn]

谢谢你的回复：
  我描述的有点问题，我的需求是不管前端有多少代理或者路由 在最后一层的nginx做代理时，能将同一个客户端的请求都代理到同一个web服务器上。Aleksandar Lazic 提供的方案正是我所需要的。



gaoping at richinfo.cn
 
From: Shafreeck Sea
Date: 2014-05-16 18:55
To: nginx at nginx.org
Subject: Re: Re: nginx1.4.7 ip_hash load balancing strategy
必须用ip_hash ? 另外我也没太看明白你的问题。


2014-05-16 16:17 GMT+08:00 gaoping at richinfo.cn <gaoping at richinfo.cn>:
ngx_http_upstream_module Load balancing algorithm upstream the instruction ip_hash;



gaoping at richinfo.cn
 
From: Shafreeck Sea
Date: 2014-05-16 16:14
To: nginx at nginx.org
Subject: Re: nginx1.4.7 ip_hash load balancing strategy
why ip_hash ?


2014-05-16 15:29 GMT+08:00 gaoping at richinfo.cn <gaoping at richinfo.cn>:
hi
     When my nginx is below this structure,Nginx access to the IP proxy server by IP, then nginx ip_hash load balancing, will all requests are routed to the same tomcat, do not know if you have what good method to solve the.
    The ip_hash function can be introduced into a custom IP.      
     Prerequisite: can not change the existing structure, and nginx access to the IP is only aproxy server, and IP client request is not true,
  


gaoping at richinfo.cn

_______________________________________________
nginx mailing list
nginx at nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx


_______________________________________________
nginx mailing list
nginx at nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20140519/f8ba9aea/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nginx??(05-16-16(05-19-08-44-38).png
Type: image/png
Size: 12535 bytes
Desc: not available
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20140519/f8ba9aea/attachment-0001.png>