I've got the follow config in testing which works.
frontend tester 10.13.200.53:80
acl url_7095 path_beg -i /7095
acl url_7096 path_beg -i /7096
acl url_7097 path_beg -i /7097
use_backend vidserver_7095 if url_7095
use_backend vidserver_7096 if url_7096
use_backend vidserver_7097 if
On 1/12/2012 12:38 PM, Willy Tarreau wrote:
But clearly if you want to map specific URL prefixes to specific servers,
at one point you need to establish this mapping and I don't see how to
simplify it further. Also I'd say that 40 lines is not *that* dramatic,
I've already seen multi-megabytes
On 6/6/2013 12:08 AM, Vincent Bernat wrote:
Hi!
If you want to use prebuilt packages for HAProxy for Debian or Ubuntu,
here is what is available:
If you want HAProxy 1.4:
1. For Debian Sid (unstable) and Debian Jessie (testing), just apt-get
install haproxy.
2. For Debian Wheezy
I'm seeing an very odd and consistent 10 second time to negotiate a
websocket connection when using HAproxy, but only when I have more than
one server in the rotation.
Going directly to the server from the browser, I connect immediately.
With only one server in the haproxy backend, I connect
On 6/12/2013 10:40 AM, Lukas Tribus wrote:
Hi Ramin,
When I have two servers in the backend haproxy makes connections to both
websocket backends and exactly 10 seconds after the client had
negotiated the connection to haproxy the client considers itself
connected to socket.io application.
On 4/14/2014 2:27 PM, Jonathan Matthews wrote:
Hi all -
I've been running 1.4 for a number of years, but am pondering moving
some as-yet-unreleased apps to 1.5, for SSL and ACL-ish reasons.
I'd like to ask how you, 1.5 sysadmins and devs, track the development
version, and how you decide which
It's easy to build your own packages with the files from the PPA which
is what we do. BTW, thanks Vincent for doing the groundwork.
Simplest method might be:
- Decide which archs you need to target. Follow a how-to for setting up
a environment to build deb packages. I recommend dedicating a
set.
Ramin
On 4/16/2014 1:25 PM, pablo platt wrote:
So I only need to setup a VM, download a file from a personal PPA, add
the source code and learn how to build a deb package...
And every user need to do the same...
Easy :)
On Wed, Apr 16, 2014 at 11:12 PM, Ramin K ramin-l...@badapple.net
Loads simpler to do the following:
## /etc/haproxy/haproxy.cfg
global
log /dev/log local0 notice
## /etc/rsyslog.d/49-haproxy.conf
# Create an additional socket in haproxy's chroot in order
# to allow logging via /dev/log to chroot'ed HAProxy processes
$AddUnixListenSocket
On 1/3/18 10:10 AM, Philipp Buehler wrote:
Am 03.01.2018 17:39 schrieb Lukas Tribus:
To compile Haproxy 1.8 with threads, at least GCC 4.7 is needed.
CentOs 6 only ships GCC 4.4.7, therefor compilation fails.
Waaah, thanks for telling before I tried to rush 1.8 to customer :-P
Rather not in
10 matches
Mail list logo