I'm answering myself :
Le 11/11/2014 15:04, Hoggins! a écrit : > Wow ! > > That's fast ! It's a very positive aspect of HAProxy : its community. > > Anyway, thanks for these answers, Baptiste and Lukas. It's almost > working as expected, except that I guess I need to use some sort of > Apache's ProxyPass equivalent, because my new backend does not > understand that query with a different path from what it is used to be > serving. > > I'll have a look at > http://blog.haproxy.com/2014/04/28/howto-write-apache-proxypass-rules-in-haproxy/. > So far, it looks quite obscure to me. I just want my backend to have a > "/" path in its incoming request, and not "/foo/", actually. But I'm > going to find this out. > > Cheers ! Just needed to add : reqirep ^([^\ :]*)\ /foo/(.*) \1\ /\2 on the backend section. > > > Le 11/11/2014 14:40, Baptiste a écrit : >> > On Tue, Nov 11, 2014 at 2:07 PM, Hoggins! <fucks...@wheres5.com> wrote: >>> >> Hello folks, >>> >> >>> >> I'm not sure what to use, and if it's possible. >>> >> >>> >> I have a website : http://www.radiom.fr. The whole site is served by a >>> >> couple of backend servers. Everything works fine. >>> >> I would like to know if it's possible to have http://www.radiom.fr/foo/ >>> >> served by another backend. >>> >> >>> >> Thank you for your hints ! >>> >> >>> >> Hoggins! >>> >> >> > Hi Hoggins, >> > >> > You can match some content using ACLs and use the use_backend keyword >> > to route traffic to an other farm. >> > To match /foo/, a specific ACL can be used: >> > acl foo path_beg -i /foo/ >> > use_backend bk_foo if foo >> > >> > this is the equivalent of >> > use_backend bk_foo if { path_beg -i /foo/ } >> > >> > Baptiste >> > Thanks, everyone !
signature.asc
Description: OpenPGP digital signature
