Hello,
I have some rare requests with logs like:
- Termination flags=SC
- Server=
- Retries=0
- Th=0
- Ti=10-50 (just normal values)
- TR=0
- Other timings = -1
It happens in 2 cases
1. With remote backends, where it is probably a real problem (once for millions
requests at average).
- According
Hello,
Here is a simple patch to add a Makefile target to run all "*.vtc"
regression testing files found in 'reg-tests' directory.
It comes with a first VTC file in relation with f874a83 bug fix commit
for LUA. This VTC file parent directory is 'reg-tests/lua'.
I have copied and pasted the
Yes, that's the plan :)
Just need to know if there is any dependency on the system and haproxy
version.
On Mon 18 Jun, 2018, 10:03 PM Gibson, Brian (IMS),
wrote:
> You’d have to ask the standard repository maintainers for that answer.
> IMO though it’s trivial to compile so if you need it why n
Full support of 6 ended in May, 2016 and Maint Support Lvl 1 ended May,
2017. It's now in the last period of retirement support, lvl 2... which
does last until Nov, 2020, but updates are only going to be for very
major security related things (and it's highly subjective).
Most enterprise user
You’d have to ask the standard repository maintainers for that answer. IMO
though it’s trivial to compile so if you need it why not just compile it
yourself?
From: Vijay Bais [mailto:vija...@endurance.com]
Sent: Monday, June 18, 2018 12:28 PM
To: haproxy@formilux.org
Subject: Haproxy 1.8 rpm fo
Hello,
Is there a particular reason for no standard rpm available of haproxy-1.8
on CentOS 6?
Any inputs will be appreciate.
Thanks,
Vijay B
> On 18 Jun 2018, at 15:38, Emmanuel Hocdet wrote:
>
>
>> Le 18 juin 2018 à 15:30, Thierry Fournier a
>> écrit :
>>
>>
>>
>>> On 18 Jun 2018, at 14:37, Emmanuel Hocdet wrote:
>>>
Le 18 juin 2018 à 10:43, Thierry Fournier
a écrit :
> On 18 Jun 2018, at
> Le 18 juin 2018 à 15:30, Thierry Fournier a
> écrit :
>
>
>
>> On 18 Jun 2018, at 14:37, Emmanuel Hocdet wrote:
>>
>>>
>>> Le 18 juin 2018 à 10:43, Thierry Fournier a
>>> écrit :
>>>
>>>
On 18 Jun 2018, at 10:33, Willy Tarreau wrote:
On Sun, Jun 17, 2018 at 09:44:50P
> On 18 Jun 2018, at 14:37, Emmanuel Hocdet wrote:
>
>>
>> Le 18 juin 2018 à 10:43, Thierry Fournier a
>> écrit :
>>
>>
>>> On 18 Jun 2018, at 10:33, Willy Tarreau wrote:
>>>
>>> On Sun, Jun 17, 2018 at 09:44:50PM +0200, thierry.fourn...@arpalert.org
>>> wrote:
Finally, I got it !
> Le 18 juin 2018 à 10:43, Thierry Fournier a
> écrit :
>
>
>> On 18 Jun 2018, at 10:33, Willy Tarreau wrote:
>>
>> On Sun, Jun 17, 2018 at 09:44:50PM +0200, thierry.fourn...@arpalert.org
>> wrote:
>>> Finally, I got it ! It works with luck because we have 1 bug in Haproxy
>>> and 1 error
On Mon, Jun 18, 2018 at 01:10:21PM +0200, Emmanuel Hocdet wrote:
> > good catch!
> > I see some strange things on my code now. I check that.
> >
>
> I find one, and tag it MEDIUM because it could have random impact on ssl.
> It's only for 1.9.
Applied, thanks Manu!
Willy
> Le 18 juin 2018 à 11:49, Emmanuel Hocdet a écrit :
>
>
> Hi Thierry, Willy
>
>> Le 18 juin 2018 à 10:43, Thierry Fournier a
>> écrit :
>>
>> Yes, including the Friday :-) But I hope this path improve stability. If
>> someone
>> have time and is interested by the subject, it may be intere
Hi Thierry, Willy
> Le 18 juin 2018 à 10:43, Thierry Fournier a
> écrit :
>
>
>> On 18 Jun 2018, at 10:33, Willy Tarreau wrote:
>>
>> On Sun, Jun 17, 2018 at 09:44:50PM +0200, thierry.fourn...@arpalert.org
>> wrote:
>>> Finally, I got it ! It works with luck because we have 1 bug in Hapro
> On 18 Jun 2018, at 10:33, Willy Tarreau wrote:
>
> On Sun, Jun 17, 2018 at 09:44:50PM +0200, thierry.fourn...@arpalert.org wrote:
>> Finally, I got it ! It works with luck because we have 1 bug in Haproxy
>> and 1 error (I suppose) in a OpenSSL compatibility layer.
> (...)
>> I join two patch
On Sun, Jun 17, 2018 at 09:44:50PM +0200, thierry.fourn...@arpalert.org wrote:
> Finally, I got it ! It works with luck because we have 1 bug in Haproxy
> and 1 error (I suppose) in a OpenSSL compatibility layer.
(...)
> I join two patch. The first which fix the cipher capture must be
> backported
On Sun, Jun 17, 2018 at 10:27:20PM +0200, Thierry Fournier wrote:
> I read the ML too quicky, thiss is the right patch.
OK applied, thanks guys.
Willy
16 matches
Mail list logo
