Hi Joel,
Unfortunately, this kind of configuration is not doable.
Could you tell us why you want to do such thing, what is the real
need for this (even if I have some ideas about it ;) )
cheers
Hi,
For this type of matching, I would rather use path_beg, which will be
much more efficient:
acl use_server_1 path_beg /q/a /q/b /q/c
use backend server1 if user_server_1
acl use_server_2 path_beg /q/x /q/y
use backend server2 if user_server_2
Or just update your regex to the example below
acl
Hi there,
after half a day of debugging (and subsequently kicking myself), I
finally noticed that whenever HAProxy (1.5-dev12 in this case)
encounters an unknown option on a bind line, it will error out with this
message irregardless of OpenSSL being enabled or not:
[ALERT] 296/194609 (6625)
On Tue, Oct 23, 2012 at 4:02 PM, Mariusz Gronczewski wrote:
> 2012/10/23 Thomas Heil :
>> Hi,
>>
>> On 23.10.2012 13:55, Finn Arne Gangstad wrote:
>>>
>>> Each request is a reasonably simple GET request that typically takes
>>> 10-20ms to process. This works great until a server needs to GC, then
Hello!
I am running haproxy-1.4.22 with option accept-invalid-http-request turned on
(the default).
It seems that haproxy successfully validates requests with unencoded '%'
characted in it:
http://some.host.net/api/v1/do_smth?lang=en-ru&text=100%%20Pure%20Mulberry%20Queen
(note unencoded %
On 24 October 2012 16:03, Dmitry Sivachenko wrote:
> Hello!
>
> I am running haproxy-1.4.22 with option accept-invalid-http-request turned
> on (the default).
Do you actually mean "off" here?
> It seems that haproxy successfully validates requests with unencoded '%'
> characted in it:
>
> http:/
I am not familiar with Java application servers, so please excuse my ignorance.
Is it possible to schedule the garbage collection? If so, you could
temporarily disable the server, kick off GC, then re-enable the
server. HAProxy has a stats socket that would allow you to adjust the
server's weight
On 24.10.2012 19:13, Jonathan Matthews wrote:
On 24 October 2012 16:03, Dmitry Sivachenko wrote:
Hello!
I am running haproxy-1.4.22 with option accept-invalid-http-request turned
on (the default).
Do you actually mean "off" here?
Yes, sorry.
It seems that haproxy successfully validat
Or better, use the disable-on-404 a few seconds before the garbage
collector restart occurs...
Baptiste
On Wed, Oct 24, 2012 at 5:19 PM, Ben Timby wrote:
> I am not familiar with Java application servers, so please excuse my
> ignorance.
>
> Is it possible to schedule the garbage collection? If
Hello!
I have two read only mysql servers behind a haproxy.
client: public IP
haproxy: public IP/private for mysql
mysql: private IP
All involved machines run Linux 3.2
A small number of servers use them.
The whole setup is not yet in production.
When in production (with just one server of t
The reasons I would want them are in the original email, but here are
some more details.
1. -- Gathering of unique stats without having to define a pool twice
This would be stellar for adhoc debug. (how much traffic matches this
ACL??), but also useful for general traffic classification.
2. --
Hi Willy,
Le 24/10/2012 01:48, Willy Tarreau a écrit :
Either way, now the doc does not reflect reality, so we must address the
issue. I don't think that anything is missing anymore to have the IPv6
address parser to fill the gap. The smp_fetch_hdr() function was rewritten
precisely to address t
> Because the percent ("%") character serves as the indicator for
> percent-encoded
> octets, it must be percent-encoded as "%25" for that octet to be used as data
> within a URI.
I don't believe HAproxy understands the difference between an not-encoded "%"
or "%%"
and a correctly encoded "%25"
Hi,
You can issue a "disable server" command on the HAProxy stats socket.
It should stop receiving traffic very quickly and does not require to
restart HAProxy, it'd be taken into account on the fly.
cheers
On Wed, Oct 24, 2012 at 8:38 PM, S Ahmed wrote:
> Say I want to update code on my clu
Hi Cyril,
On Wed, Oct 24, 2012 at 08:33:57PM +0200, Cyril Bonté wrote:
> Hi Willy,
>
> Le 24/10/2012 01:48, Willy Tarreau a écrit :
> >Either way, now the doc does not reflect reality, so we must address the
> >issue. I don't think that anything is missing anymore to have the IPv6
> >address pars
Hi again,
Le 24/10/2012 23:41, Willy Tarreau a écrit :
No problem. The principle is quite simple: a fetch function is called with
a pointer to a sample in which to store the type and contents. If contents
need storage, you put them in a buffer-sized chunk returned by
sample_get_trash_chunk(). If
url2sa() mistakenly uses "addr" as a reference. This causes a segfault when
option http_proxy or url_ip are used.
This bug was introduced in haproxy 1.5 and doesn't need to be backported.
---
src/standard.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/standard.c
The information contained in this e-mail is of a confidential nature and is
intended only for the addressee. If you are not the intended addressee, any
disclosure, copying or distribution by you is prohibited and may be unlawful.
Disclosure to any party other than the addressee, whether inadv
Commit ceb4ac9c states that IPv6 values are accepted by "hdr_ip" acl,
but the code didn't allow it. This patch provides the ability to accept IPv6
values.
---
src/proto_http.c | 23 ++-
1 file changed, 18 insertions(+), 5 deletions(-)
diff --git a/src/proto_http.c b/src/prot
On Wed, Oct 24, 2012 at 11:47:47PM +0200, Cyril Bonté wrote:
> url2sa() mistakenly uses "addr" as a reference. This causes a segfault when
> option http_proxy or url_ip are used.
Wow, good catch Cyril, thanks a lot !
This is typically why I hate type casts in general and prefer unions
whenever po
20 matches
Mail list logo
