As far as i know acl doesnt work in tcp mode.
Met een vriendelijke groet, ---- Mike Hoffs Mijn-Sleutel Peperstraat 33 6678 AL Oosterhout Tel: +31 (0)24 8200208 tijdens kantoor uren (09:00 - 17:00) Mail: m.ho...@mijn-sleutel.com Website: http://www.mijn-sleutel.com <http://www.mijn-sleutel.com/> Van: shengtao [mailto:sheng...@uit.com.cn] Verzonden: vrijdag 22 oktober 2010 8:25 Aan: haproxy Onderwerp: i meet a hard problem for your help! now i have search many articles in order to solve the problem ,but~~ the server haproxy ip:192.168.0.12 /space is a context for a java web project In my proxy.cfg: frontend https_proxy bind :443 mode tcp acl is_ssl req_ssl_ver 2:3.1 tcp-request content accept if is_ssl timeout client 5m option forwardfor default_backend NginxDefine acl req_pubsub_path req_path /space use_backend USpaceDefine2 if req_pubsub_path now when i enter https://192.168.0.12 <https://192.168.0.12> ,it can turn into the NginxDefine,but when i input https://192.168.0.12/space <https://192.168.0.12/space> it can not enter! i have a try to replace the criterion "req_path" with path or url_path and so on,but i doest not matter!why ??? At last,i remember that dealing with the http request is not meet this problem: frontend https=_proxy bind :80 mode tcp timeout client 5m option forwardfor default_backend NginxDefine acl req_pubsub_path req_path /space use_backend USpaceDefine2 if req_pubsub_path i beg your ans: thanks!!!!!! 2010-10-22 ________________________________ shengtao
