On Thu, Sep 05, 2019 at 05:13:11PM +, Schimweg, Luca wrote:
> Hey,
>
> just for you to get an impression, a quick draft of what a change could look
> like:
>
> https://github.com/lucaschimweg/haproxy/commit/5306395c062ac20b6d030d48c48290d5f08db5cc
( pasted here for discussion)
> char
Hi,
On Thu, Sep 05, 2019 at 05:31:36PM +0200, Lukas Tribus wrote:
> > unique-id-format
> >
hi, any update ?
пн, 2 сент. 2019 г. в 10:56, Илья Шипицин :
> any idea how to skip "alpn" test on CentOS 6 ?
>
> (I think, I should "rm" particular reg test, however, it does not look
> nice)
>
> пн, 2 сент. 2019 г. в 00:10, Илья Шипицин :
>
>> please review the following patch
>>
>
Hey,
just for you to get an impression, a quick draft of what a change could look
like:
https://github.com/lucaschimweg/haproxy/commit/5306395c062ac20b6d030d48c48290d5f08db5cc
I didn't check with the contributing guidelines, etc... yet, but this commit
would make the feature work.
In the
Hello Luca,
On Thu, Sep 5, 2019 at 5:38 PM Schimweg, Luca wrote:
>
> Hey,
>
> i would suggest adding support for the widely used RFC4122 Version 4 UUID,
> which is generated completely random. In lua a script for generating these is
> about 5 lines long, but because of several reasons I don't
On 9/5/19 17:43, Schimweg, Luca wrote:
>
> actually, I am doing that, I generate a random number from 0-16383
> and after that I add 32768 onto it. 32768 is 0x8000,
> 32768+16383=49151 is 0xBFFF.
Ah, I missed it, sorry again.
Geoff
--
** * * UPLEX - Nils Goroll Systemoptimierung
Hey,
actually, I am doing that, I generate a random number from 0-16383 and after
that I add 32768 onto it. 32768 is 0x8000, 32768+16383=49151 is 0xBFFF. I
cannot really come up with a reason why this is too, but the specification is
fulfilled.
And yeah, we could definitely generate any other
Hey,
i would suggest adding support for the widely used RFC4122 Version 4 UUID,
which is generated completely random. In lua a script for generating these is
about 5 lines long, but because of several reasons I don't want to use lua in
this use-case.
I would definitely not add add additional
On 9/5/19 16:58, Schimweg, Luca wrote:
>
>
> unique-id-format
> %[rand,hex,bytes(8,8),lower]-%[rand(65536),hex,bytes(12,4),lower]-4%[rand(4096),hex,bytes(13,3),lower]-%[rand(16384),add(32768),hex,bytes(12,4),lower]-%[rand(65536),hex,bytes(12,4),lower]%[rand,hex,bytes(8,8),lower]
This is going
Hello,
On Thu, Sep 5, 2019 at 4:58 PM Schimweg, Luca wrote:
>
> Hey again,
>
> I tried to use rand, but when using it, my generation code for a UUID looks
> like this:
>
> unique-id-format
>
Hey again,
I tried to use rand, but when using it, my generation code for a UUID looks
like this:
unique-id-format
Hi,
I was looking at implementing rate limiting in our setup. But, since we
are handling both IPv4 and IPv6 in the same frontends and backends, I
was wondering how I could do that.
AFAIK a stick table is either IPv4 or IPv6 and you can only have one
stick table per frontend or backend.
Is
On Wed, 2019-09-04 at 21:41 +0200, Tim Düsterhus wrote:
> Conrad,
>
> Am 04.09.19 um 10:17 schrieb Conrad Hoffmann:
> > More for illustrative purposes than anything else I attached a
> > patch
> > that fixes the issue for me (against 2.0 repo). However, I have not
> > yet
> > spent a lot of time
13 matches
Mail list logo
