Thanks here a proposed patch.
Kind regards.
On Tue, 15 Jan 2019 at 13:10, Willy Tarreau wrote:
>
> Hi David,
>
> On Tue, Jan 15, 2019 at 11:12:16AM +, David Carlier wrote:
> > Hi dear list,
> >
> > A customer of use encountered an issue while compiling with the
> > DeviceAtlas module.
>
>
On Tue, Jan 15, 2019 at 01:16:05PM +, David Carlier wrote:
> Thanks here a proposed patch.
OK now merged to master and 1.9, thanks David!
Willy
Hi Willy, Tim,
I am providing some more details about my setup if you wish to try to
reproduce the issue.
As I mentioned before, I have 5 HAProxy nodes, all of them listening to
public IPs.
My DNS is setup with round-robin mode on AWS R53, resolving to one of the
HAProxy nodes individual IPs for
Hi David,
On Tue, Jan 15, 2019 at 11:12:16AM +, David Carlier wrote:
> Hi dear list,
>
> A customer of use encountered an issue while compiling with the
> DeviceAtlas module.
Ah! At least one of the device detection modules gets tested! This is
reassuring, because quite honestly I was
Hi dear list,
A customer of use encountered an issue while compiling with the
DeviceAtlas module.
Seems due to the struct buffer changes it underwent a little while ago
... Could you confirm the area member is equivalent to the previous p
one ?
Thanks in advance.
Kindest regards.
I forgot to mention, might be obvious though, to b backported to 1.9. Cheers.
On Tue, 15 Jan 2019 at 13:16, David Carlier wrote:
>
> Thanks here a proposed patch.
>
> Kind regards.
>
> On Tue, 15 Jan 2019 at 13:10, Willy Tarreau wrote:
> >
> > Hi David,
> >
> > On Tue, Jan 15, 2019 at
Hi Emerson,
On Tue, Jan 15, 2019 at 12:21:07PM +0100, Emerson Gomes wrote:
> Hi Willy, Tim,
>
> I am providing some more details about my setup if you wish to try to
> reproduce the issue.
> As I mentioned before, I have 5 HAProxy nodes, all of them listening to
> public IPs.
> My DNS is setup
Hello Emerson,
On Mon, Jan 14, 2019 at 10:26:40PM +0100, Emerson Gomes wrote:
> Hello Tim,
>
> Sorry for the delayed answer.
> The segfaults I had experinced apparently were related to something else -
> Maybe some issue in my env.
> At first I tried to apply the patch to 1.9.0, but after
Hi again,
On Sat, Dec 15, 2018 at 05:09:07PM +0100, Willy Tarreau wrote:
> Hi Norman,
>
> On Thu, Dec 06, 2018 at 04:57:18PM +, Norman Branitsky wrote:
> > NGINX just announced the following load balancing method as default for
> > their Ingress Controller for Kubernetes.
> > Will this
Thanks a lot. Do you have a rough ETA for 1.9.2. ?
Sorry for pressure Willy :-), thanks to dyndynamic for pointing it out.
On Tue, 15 Jan 2019 at 14:09, Willy Tarreau wrote:
>
> On Tue, Jan 15, 2019 at 01:16:05PM +, David Carlier wrote:
> > Thanks here a proposed patch.
>
> OK now merged
On Tue, Jan 15, 2019 at 04:07:42PM +, David Carlier wrote:
> Thanks a lot. Do you have a rough ETA for 1.9.2. ?
Expected tomorrow, with no guarantees of course. Nothing critical
in the queue this time, this leaves us with enough time to consider
backports ;-)
> Sorry for pressure Willy :-),
On Tue, Jan 15, 2019 at 08:13:03PM +, Laurent Penot wrote:
> Hi David, Willy,
>
> Thanks a lot for the quick feedback, I can now compile successfully haproxy
> 1.9 from master with device atlas __
Great, thank you for the feedback!
Willy
Willy,
Am 15.01.19 um 15:32 schrieb Willy Tarreau:
> Got it! I thought the problem was local to a process and that we
> replicated bad data, but in fact not, it's a distributed race. In
> this case there is no other short-term solution, and the drift has
> no reason to significantly accumulate
Hi David, Willy,
Thanks a lot for the quick feedback, I can now compile successfully haproxy 1.9
from master with device atlas __
Best regards
Laurent
On 15/01/2019 17:20, "Willy Tarreau" wrote:
On Tue, Jan 15, 2019 at 04:07:42PM +, David Carlier wrote:
> Thanks a lot. Do you
Hi Tim,
On Tue, Jan 15, 2019 at 09:32:42PM +0100, Tim Düsterhus wrote:
> Willy,
>
> Am 15.01.19 um 15:32 schrieb Willy Tarreau:
> > Got it! I thought the problem was local to a process and that we
> > replicated bad data, but in fact not, it's a distributed race. In
> > this case there is no
Willy,
Am 15.01.19 um 21:41 schrieb Willy Tarreau:
>> Ideally the peers would exchange their local values, only.
>
> Yes and that's how this currently works.
I believe they exchange what they believe to be the current global
connection count, instead of their local connection count, no?
>>
On Tue, Jan 15, 2019 at 09:51:12PM +0100, Tim Düsterhus wrote:
> Willy,
>
> Am 15.01.19 um 21:41 schrieb Willy Tarreau:
> >> Ideally the peers would exchange their local values, only.
> >
> > Yes and that's how this currently works.
>
> I believe they exchange what they believe to be the
Hi,
I have other problem. I want to only allow some ip access my website. Please
show me how to allow some IP by domain name.
I try with: tcp-request connection reject if { hdr(host) crmone.thaison.vn } !{
src x.x.x.x x.x.x.y } but it’s not work. I get error message:
How to reproduce:
1. Start browser-download (content-disposition: attachment) of some big file
through H2
* Tested with 1Gb file and several Chrome-versions (67-)
2. Make reload
3. Process with this connection would stay, transfer everything successfully
and even send to log info about code-200
Dear,
I fixed it. I use { src x.x.x.x ... } in use_backend and it worked.
Many thanks,
-Original Message-
From: Vũ Xuân Học
Sent: Wednesday, January 16, 2019 10:37 AM
To: 'Aleksandar Lazic' ; 'haproxy@formilux.org'
; 'PiBa-NL'
Subject: RE: Get client IP
Hi,
I have other problem.
Le 14/01/2019 à 21:53, PiBa-NL a écrit :
Hi Christopher,
Op 14-1-2019 om 11:17 schreef Christopher Faulet:
Le 12/01/2019 à 23:23, PiBa-NL a écrit :
Hi List,
I've configured haproxy with htx and when i try to filter the stats
webpage.
Sending this request: "GET /?;csv;scope=b1" to
21 matches
Mail list logo
