Re: could haproxy call redis for a result?

nginx would be more suitable for something like this. It even has a redis plugin: http://wiki.nginx.org/HttpRedis Perhaps you can achieve your functionality with the redis_next_upstream parameter. Sergej On Tue, May 8, 2012 at 4:39 AM, S Ahmed wrote: > I agree it will add overheard for each c

Re: req_proto_http does not work

On Thu, Jun 10, 2010 at 8:45 PM, Willy Tarreau wrote: > On Thu, Jun 10, 2010 at 06:39:09PM +0200, Rapsey wrote: > > hello, > > > > This configuration will always send to backend tcpback, if I run curl > > http://127.0.0.1 > > > > frontend tcpfront *:80 >

req_proto_http does not work

hello, This configuration will always send to backend tcpback, if I run curl http://127.0.0.1 frontend tcpfront *:80 acl acl_ishttp req_proto_http use_backend nginx if acl_ishttp default_backend tcpback The string that curl sends is GET / HTTP/1.1\r\nUser-Agent: curl/7

Re: layer 7 proxy hierarchy

he proxy configuration. > > I'll look some more, though, thank you for the pointer. > > On Wed, Jun 9, 2010 at 2:58 AM, Rapsey wrote: > > You can't do this with haproxy, but you can with nginx and > X-Accel-Redirect > > > > > > Sergej > > > >

Re: layer 7 proxy hierarchy

You can't do this with haproxy, but you can with nginx and X-Accel-Redirect Sergej On Wed, Jun 9, 2010 at 5:17 AM, Jonah Benton wrote: > Greetings, > > I have several web applications that each service different portions > of the same taxonomy. The taxonomy is very deep- millions of > resource

Re: no trailing slash results in 301

Oh it's not a haproxy issue but a webserver one. Because it detects a directory at that location, it will redirect back to itself, with the same URL and add a trailing slash. Unfortunately the server is at 8080 and it will add that port also. Sergej On Thu, Jul 23, 2009 at 4:39 PM, R

no trailing slash results in 301

http://somewebaddress/test will result in a 301 to the server for which haproxy should be proxying requests. So the user is redirected to http://localhost:8080/test. http://somewebaddress/test/ works fine. I tried backend nginx and apache and it is the same. Anyone have an idea whats going on? My

Re: make on os x

Even with darwin kqueue was not enabled, I tried it. Why is there even a separate osx makefile if the default one works? Sergej On Thu, Jul 23, 2009 at 1:20 PM, Willy Tarreau wrote: > On Thu, Jul 23, 2009 at 08:40:23AM +0200, Rapsey wrote: > > Yes thank you. I figured it out event

Re: make on os x

Tested it on darwin and leopard and I haven't noticed any problems. Sergej On Thu, Jul 23, 2009 at 7:17 AM, Willy Tarreau wrote: > Hi, > > On Thu, Jun 11, 2009 at 09:51:00AM +0200, Rapsey wrote: > > Sorry error in -vv output, TARGET = darwin > > > > Sergej > &g

Re: make on os x

Sorry error in -vv output, TARGET = darwin Sergej On Thu, Jun 11, 2009 at 9:46 AM, Rapsey wrote: > I'm trying to build haproxy with kqueue on osx leopard, but I don't think > it's working. There is no mention of DENABLE_KQUEUE anywhere when it's > building it. >

make on os x

I'm trying to build haproxy with kqueue on osx leopard, but I don't think it's working. There is no mention of DENABLE_KQUEUE anywhere when it's building it. This is the make I use: make Makefile.osx TARGET=darwin CPU=i686 USE_PCRE=1 all checking the executable after make: > ./haproxy -vv HA-Prox