At Loadbalancer.org we simulate WCCP support (i.e. put your proxy in
WCCP mode and it will automatically accept traffic from the load
balancer:) by using:
LVS in DR mode with firewall marks + force ALL traffic for any IP to
the local_in...
This gives full transparent proxy aka. WCCP. (without
Le 11/07/2011 22:07, Willy Tarreau a écrit :
On Mon, Jul 11, 2011 at 02:20:37PM +0200, Damien Hardy wrote:
Whatever method is used, I want that haproxy never ask to any backend an
answer directly to client and log the request like others
Then define a monitor-uri, it's done for that.
On Tue, Jul 12, 2011 at 08:56:12AM +0200, Damien Hardy wrote:
frontend XXX
mode http
monitor-uri /test
All checks to /test will return a 200 OK. Its used so that haproxy can be
tested by other components (eg: keepalived).
Regards,
Willy
Yes but if I refer
2011/7/12 Willy Tarreau w...@1wt.eu
Then you can use the errorfile method : you send your request to a
backend without any server (which will produce an error 503) and you
use errorfile 503 /path/to/file to return this file instead of the
error 503. Some people use this to serve a few static
On Tue, Jul 12, 2011 at 10:42:31AM +0200, Damien Hardy wrote:
2011/7/12 Willy Tarreau w...@1wt.eu
Then you can use the errorfile method : you send your request to a
backend without any server (which will produce an error 503) and you
use errorfile 503 /path/to/file to return this file
2011/7/12 Willy Tarreau w...@1wt.eu
On Tue, Jul 12, 2011 at 10:42:31AM +0200, Damien Hardy wrote:
2011/7/12 Willy Tarreau w...@1wt.eu
Then you can use the errorfile method : you send your request to a
backend without any server (which will produce an error 503) and you
use
On Tue, Jul 12, 2011 at 03:16:54PM +0200, Damien Hardy wrote:
I have done some tests.
The errorfile 503 directive on empty backend do the job from the client
point of view but to be very perfect I would like there is no 503 error code
in my haproxy logs.
OK I see. You want something even
Hi.
I've got such a scheme on the shared hosting:
+- apache_pool1
|
apache_fe - haproxy -|- apache_pool2
|
+- apache_pool3
...
haproxy.conf:
defaults
log 127.0.0.1 local1 notice
Hi,
According to HAProxy logs, your errors seems application related:
SH The server aborted before sending its full HTTP response headers, or
it crashed while processing the request. Since a server aborting at
this moment is very rare, it would be wise to inspect its
Hi Alexey,
On Tue, Jul 12, 2011 at 11:36:16PM +0400, Alexey Vlasov wrote:
Hi.
I've got such a scheme on the shared hosting:
+- apache_pool1
|
apache_fe - haproxy -|- apache_pool2
|
+- apache_pool3
10 matches
Mail list logo