Re: Help haproxy

+01:00 Yuan Long yuan.l...@chinanetcloud.com: Do you have the words option forward for in your config. http://cbonte.github.io/haproxy-dconv/configuration-1.5.html#option%20forwardfor Can you copy/paste your config (without sensitive info if needed). Regards

Re: Help haproxy

Do you have the words option forward for in your config. http://cbonte.github.io/haproxy-dconv/configuration-1.5.html#option%20forwardfor Can you copy/paste your config (without sensitive info if needed). Regards, Long

Re: Url load balancer

http://www.haproxy.org/#plat Regards, Long Wu Yuan 龙 武 缘 Sr. Linux Engineer 高级工程师 ChinaNetCloud 云络网络科技(上海)有限公司 | www.ChinaNetCloud.com1238 Xietu Lu, X2 Space 1-601, Shanghai, China | 中国上海市徐汇区斜土路1238号X2空 间1-601室 24x7

Re: Url load balancer

**|* www.ascotel.com.jo [image: facebook] https://www.facebook.com/ASCOTELJORDAN?fref=ts [image: twitter] https://twitter.com/ASCOTELjo http://www.ascotel.com.jo/ *From:* Yuan Long [mailto:yuan.l...@chinanetcloud.com] *Sent:* Tuesday, January 27, 2015 12:15 PM *To:* mohammad Atiyat *Cc:* haproxy

Re: Stick tables, good guys, bad guys, and NATs

I am in the same fix. No matter what we try, the data to address is the real laptop/desktop/cellphone/server count. That count is skewed as soon as there are a hundred laptops/desktops behind a router. Best I heard is from Willy himself, suggestion to use base32+src. At the cost of losing plain

Re: haproxy-systemd-wrapper with -sf causes it to exit and print usage info

$ /etc/init.d/haproxy Usage: /etc/init.d/haproxy {start|stop|status|restart|try-restart|reload|force-reload} $ Are reload/force-reload not enough. Regards, Long Wu Yuan 龙 武 缘 Sr. Linux Engineer 高级工程师 ChinaNetCloud

Re: haproxy rpm

THis was enough for me http://pkgs.org/search/haproxy Regards, Long Wu Yuan 龙 武 缘 Sr. Linux Engineer 高级工程师 ChinaNetCloud 云络网络科技(上海)有限公司 | www.ChinaNetCloud.com1238 Xietu Lu, X2 Space 1-601, Shanghai, China |

Re: rate-limiting by checking both src-ipaddress path-requested at the same time

:00:36PM +0800, Yuan Long wrote: Hi Willy, You answered a question, in record time, a short while ago, for a colleague, related to the MSIE encoding workaround option accept-invalid-http-request. No pb. Next time you'd better post the question on the mailing list, because it's much more

rate-limiting - per src per path

Hi, Is it possible to rate-limit requests per-path-per-src. Sticky-table can be type IP or type String. tcp-request can be either connection or content. I am not an expert and hence the doubt. There are examples on the web but not explained if both src and path can be checked for rate-limiting.