Hi, I'm trying to figure out whether the following tuneables apply only to
bound HTTP sockets ou
tune.h2.header-table-size
tune.h2.initial-window-size
tune.h2.max-concurrent-streams
Hi Willy,
> Em 30 de out de 2019, à(s) 01:41, Willy Tarreau escreveu:
>
> Hi Joao,
>
> On Tue, Oct 29, 2019 at 09:10:11PM -0300, Joao Morais wrote:
>>
>> What I need to implement is a way to share the sticky session cookie between
>> two distinct but related domains, say haproxy.org and
I had come to think that haproxy was not parsing a Truncate-flagged DNS
response that had usable entries in it.
After further investigation, tcpdump made clear that the truncated DNS
response enumerated *no* 'A' records, expecting the client to switch to TCP
for the query.
So we'll be looking at
Just wanted to see what you thought of the below. Hope you are well!
P.O. Box 135, Whitianga 3510, New Zealand | To unsubscribe please reply
with 'Unsubscribe' in the header
On Thursday, October 24, 2019 at 10:45 AM, Jen Miller
wrote:
> Dear Editor,
>
> My name is Jen and I’m an Editor at
hi,
is anybody running things like
https://www.poppelgaard.com/microsoft-scvmm-2012citrix-netscaler-o ?
I mean using SCVMM in so called "services management", i.e. dataplane api ?
thanks,
Ilya Shipitsin
On Wed, Oct 30, 2019 at 4:48 PM David Birdsong
wrote:
>
> On Wed, Oct 30, 2019 at 11:39 AM Baptiste wrote:
>
>> Thanks!
>>>
>>> It had that feel to it...seemed like a cache lock timeout and/or somehow
>>> tied to the request interval.
>>>
>>>
>> I think I know where to fix this behavior in the
It can be sometimes interesting to have a timestamp with a
resolution of less than a second.
It is currently painful to obtain this, because concatenation
of date and date_us lead to a shorter timestamp during first
100ms of a second, which is not parseable and needs ugly ACLs
in configuration to
On Wed, Oct 30, 2019 at 11:39 AM Baptiste wrote:
> Thanks!
>>
>> It had that feel to it...seemed like a cache lock timeout and/or somehow
>> tied to the request interval.
>>
>>
> I think I know where to fix this behavior in the code. I will work on the
> "how to fix it" later tonight.
> In the
>
> Thanks!
>
> It had that feel to it...seemed like a cache lock timeout and/or somehow
> tied to the request interval.
>
>
I think I know where to fix this behavior in the code. I will work on the
"how to fix it" later tonight.
In the meantime, you can apply the workaround below. This is doable
On Wed, Oct 30, 2019, 9:58 AM Baptiste wrote:
>
>
> On Tue, Oct 29, 2019 at 8:18 PM David Birdsong
> wrote:
>
>> I should have put the haproxy version in the mail too:
>>
>> haproxy 2.0.8
>>
>> On Tue, Oct 29, 2019 at 3:07 PM David Birdsong
>> wrote:
>>
>>> I've narrowed down a behavior that I
On Tue, Oct 29, 2019 at 8:18 PM David Birdsong
wrote:
> I should have put the haproxy version in the mail too:
>
> haproxy 2.0.8
>
> On Tue, Oct 29, 2019 at 3:07 PM David Birdsong
> wrote:
>
>> I've narrowed down a behavior that I think might be a bug, but is
>> definitely not ideal.
>>
>> This
Hi,
On Tue, Oct 29, David Birdsong wrote:
> I've narrowed down a behavior that I think might be a bug, but is
> definitely not ideal.
>
> This minimal configuration copies header: X-Host into Host and performs a
> dynamic DNS query against that field name, stores the output in a txn var,
> and
hello,
are there any plans to participate GSoC 2020 ?
thanks,
Ilya Shipitsin
13 matches
Mail list logo