On 15 January 2014 07:36, Rakesh G K wrote:
> Hello,
> Is it possible to forward an incoming request to the backend by retaining
> the URL path in http mode?.
> Using ACLs I was able to categorize the incoming requests to different
> rulesets, but on using a specific backend for a certain URL part
Hi,
"option accept-invalid-http-response"
was the solution.
Regards,
Florian
On 14.01.2014 17:31, Florian Engelmann wrote:
Hi,
we are using HAProxy 1.5-dev21 as loadbalancer frontend and some NGINX
1.4 servers as backend. Everything is working perfect. Great piece of
software!
One question:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Iam running HAPRoxy with eglibc and commit
4448925930655dec57847ed41a34a24a8169d053, aka
BUILD/MINOR: listener: remove a glibc warning on accept4() introduces an
fatal error on building.
The message I get is
- --
include -DCONFIG_HAPROXY_VERSIO
Hi,
Now you can use map for your needs. The maps can be manipulated via the
"stats socket". The identifier of the map is the file name:
acl abuser src,map_ip_int(abusers.lst,0) -m int eq 1
http-request tarpit if abuser
The file abusers.lst is empty file, or contain the known blocked IP.
D
Hi,
awesome ! thanks for the help, i'm gonna try it asap :D
Regards.
2014/1/15 Thierry FOURNIER :
> Hi,
>
> Now you can use map for your needs. The maps can be manipulated via the
> "stats socket". The identifier of the map is the file name:
>
>acl abuser src,map_ip_int(abusers.lst,0) -m int
It should be considered as a temporary workaround until you fix your broken
application.
Baptiste
Le 15 janv. 2014 11:20, "Florian Engelmann"
a écrit :
> Hi,
>
> "option accept-invalid-http-response"
>
> was the solution.
>
> Regards,
> Florian
>
> On 14.01.2014 17:31, Florian Engelmann wrote:
On 14.01.2014 15:01, Timh Bergström wrote:
> I would really love a clean/native way to basically do "includes" in
> the configuration file;
+1 on what Timh said.
7 matches
Mail list logo