Re: acl using path_beg
Got it working. the issue was a lot chained acls that were catching up the rule I was just adding. Thank you all for your help. On Mon, Aug 1, 2011 at 5:05 PM, Gabriel Sosa wrote: > well, > > is it not redirecting. just die there with a 404 status > > any other hint? > > regards > > On Sun, Jul 31, 2011 at 7:01 PM, Baptiste wrote: >> Hi, >> >> The wp-admin page of wordpress is a 302 redirecting to "wp-login.php". >> >> Have you tried to browse the backend directly? >> I guess it should not work. >> >> There are some parameters on Wordpress to tell him on which URL it >> will be hosted. >> By default, it may be "/", in your case you should turn this parameter >> to "/blog" :) >> >> cheers >> >> >> On Sun, Jul 31, 2011 at 11:46 PM, Gabriel Sosa wrote: >>> Hello folks >>> >>> I'm trying to send all the traffic that starts with /blog to a >>> specific backend and I'm using *path_beg* for that. here is a snip of >>> my config file: >>> >>> defaults >>> log global >>> timeout client 6 >>> timeout server 3m >>> timeout connect 15000 >>> retries 3 >>> option redispatch >>> >>> >>> frontend http >>> mode http >>> log global >>> option httplog >>> option >>> forceclose >>> option >>> httpclose >>> >>> bind XXX.XXX.XXX.XXX:80 # com 80 >>> >>> acl blog_acl path_beg /blog >>> use_backend blog_backend if blog_acl >>> default_backend farm80 >>> >>> >>> >>> >>> For some reason, if I browse http://www.example.com/blog everything >>> works just fine, but if I browse http://www.example.com/blog/wp-admin/ >>> (as you can guess I'm using wordpress) I get a 404 status. >>> >>> AFAIK, the acl path_beg /blog should match /blog/ or /blog/wp-admin >>> basically anything after /blog/ should be sent to that backend. >>> >>> do you have any idea why that could be not working as expected? >>> >>> Best regards >>> >>> -- >>> Gabriel Sosa >>> Si buscas resultados distintos, no hagas siempre lo mismo. - Einstein >>> >>> >> > > > > -- > Gabriel Sosa > Si buscas resultados distintos, no hagas siempre lo mismo. - Einstein > -- Gabriel Sosa Si buscas resultados distintos, no hagas siempre lo mismo. - Einstein
Re: acl using path_beg
well, is it not redirecting. just die there with a 404 status any other hint? regards On Sun, Jul 31, 2011 at 7:01 PM, Baptiste wrote: > Hi, > > The wp-admin page of wordpress is a 302 redirecting to "wp-login.php". > > Have you tried to browse the backend directly? > I guess it should not work. > > There are some parameters on Wordpress to tell him on which URL it > will be hosted. > By default, it may be "/", in your case you should turn this parameter > to "/blog" :) > > cheers > > > On Sun, Jul 31, 2011 at 11:46 PM, Gabriel Sosa wrote: >> Hello folks >> >> I'm trying to send all the traffic that starts with /blog to a >> specific backend and I'm using *path_beg* for that. here is a snip of >> my config file: >> >> defaults >> log global >> timeout client 6 >> timeout server 3m >> timeout connect 15000 >> retries 3 >> option redispatch >> >> >> frontend http >> mode http >> log global >> option httplog >> option >> forceclose >> option >> httpclose >> >> bind XXX.XXX.XXX.XXX:80 # com 80 >> >> acl blog_acl path_beg /blog >> use_backend blog_backend if blog_acl >> default_backend farm80 >> >> >> >> >> For some reason, if I browse http://www.example.com/blog everything >> works just fine, but if I browse http://www.example.com/blog/wp-admin/ >> (as you can guess I'm using wordpress) I get a 404 status. >> >> AFAIK, the acl path_beg /blog should match /blog/ or /blog/wp-admin >> basically anything after /blog/ should be sent to that backend. >> >> do you have any idea why that could be not working as expected? >> >> Best regards >> >> -- >> Gabriel Sosa >> Si buscas resultados distintos, no hagas siempre lo mismo. - Einstein >> >> > -- Gabriel Sosa Si buscas resultados distintos, no hagas siempre lo mismo. - Einstein
Re: acl using path_beg
Hi, The wp-admin page of wordpress is a 302 redirecting to "wp-login.php". Have you tried to browse the backend directly? I guess it should not work. There are some parameters on Wordpress to tell him on which URL it will be hosted. By default, it may be "/", in your case you should turn this parameter to "/blog" :) cheers On Sun, Jul 31, 2011 at 11:46 PM, Gabriel Sosa wrote: > Hello folks > > I'm trying to send all the traffic that starts with /blog to a > specific backend and I'm using *path_beg* for that. here is a snip of > my config file: > > defaults > log global > timeout client 6 > timeout server 3m > timeout connect 15000 > retries 3 > option redispatch > > > frontend http > mode http > log global > option httplog > option > forceclose > option > httpclose > > bind XXX.XXX.XXX.XXX:80 # com 80 > > acl blog_acl path_beg /blog > use_backend blog_backend if blog_acl > default_backend farm80 > > > > > For some reason, if I browse http://www.example.com/blog everything > works just fine, but if I browse http://www.example.com/blog/wp-admin/ > (as you can guess I'm using wordpress) I get a 404 status. > > AFAIK, the acl path_beg /blog should match /blog/ or /blog/wp-admin > basically anything after /blog/ should be sent to that backend. > > do you have any idea why that could be not working as expected? > > Best regards > > -- > Gabriel Sosa > Si buscas resultados distintos, no hagas siempre lo mismo. - Einstein > >
acl using path_beg
Hello folks I'm trying to send all the traffic that starts with /blog to a specific backend and I'm using *path_beg* for that. here is a snip of my config file: defaults log global timeout client 6 timeout server 3m timeout connect 15000 retries 3 option redispatch frontend http modehttp log global option httplog option forceclose option httpclose bindXXX.XXX.XXX.XXX:80# com 80 acl blog_acl path_beg /blog use_backend blog_backend if blog_acl default_backend farm80 For some reason, if I browse http://www.example.com/blog everything works just fine, but if I browse http://www.example.com/blog/wp-admin/ (as you can guess I'm using wordpress) I get a 404 status. AFAIK, the acl path_beg /blog should match /blog/ or /blog/wp-admin basically anything after /blog/ should be sent to that backend. do you have any idea why that could be not working as expected? Best regards -- Gabriel Sosa Si buscas resultados distintos, no hagas siempre lo mismo. - Einstein
