On 2019-02-14 18:29, Aleksandar Lazic wrote:
Replaced HAproxy with Nginx for testing and with Nginx, not a single
connection
was interrupted, did millions of requests.
In 1.9.4 are a lot of fixed added.
please can you try your tests with 1.9.4, thanks.
Already did before writing my previous
On 2019/2/14 12:45, Olivier Houchard wrote:
> Hi Patrick,
>
> On Thu, Feb 14, 2019 at 09:12:18AM -0500, Patrick Hemmer wrote:
>>
>> On 2019/2/14 08:20, Frederic Lecaille wrote:
>>> On 2/14/19 1:32 PM, Frederic Lecaille wrote:
On 2/13/19 7:30 PM, Patrick Hemmer wrote:
>
> On
Am 14.02.2019 um 15:31 schrieb Veiko Kukk:
>
> On 2019-02-01 13:30, Veiko Kukk wrote:
>> On 2019-02-01 12:34, Aleksandar Lazic wrote:
>>
>>> Do you have any errors in lighthttpds log?
>>
>> Yes, it has error messages about not being enable to write to socket.
>>
>> Unrecoverable error writing to
Hi Patrick,
On Thu, Feb 14, 2019 at 09:12:18AM -0500, Patrick Hemmer wrote:
>
>
> On 2019/2/14 08:20, Frederic Lecaille wrote:
> > On 2/14/19 1:32 PM, Frederic Lecaille wrote:
> >> On 2/13/19 7:30 PM, Patrick Hemmer wrote:
> >>>
> >>>
> >>> On 2019/2/13 10:29, Olivier Houchard wrote:
> Hi
Hi Lukas,
On Thu, Feb 14, 2019 at 06:28:29PM +0100, Lukas Tribus wrote:
> Hello,
>
>
> FYI the behavior was also changed on the openssl side (and will be in 1.1.1b):
> https://github.com/openssl/openssl/commit/4af5836b55442f31795eff6c8c81ea7a1b8cf94b
>
> So applications fixes are only
Hello,
FYI the behavior was also changed on the openssl side (and will be in 1.1.1b):
https://github.com/openssl/openssl/commit/4af5836b55442f31795eff6c8c81ea7a1b8cf94b
So applications fixes are only necessary for 1.1.1a.
Lukas
Looks like apples llvm is not based on master branch.
https://news.ycombinator.com/item?id=16545037
Ursprüngliche Nachricht
Von: Frederic Lecaille
Gesendet: 14. Februar 2019 16:13:01 MEZ
An: Patrick Hemmer
CC: Olivier Houchard , Aleksandar Lazic
, haproxy@formilux.org
On 2/14/19 3:12 PM, Patrick Hemmer wrote:
On 2019/2/14 08:20, Frederic Lecaille wrote:
On 2/14/19 1:32 PM, Frederic Lecaille wrote:
On 2/13/19 7:30 PM, Patrick Hemmer wrote:
On 2019/2/13 10:29, Olivier Houchard wrote:
Hi Patrick,
On Wed, Feb 13, 2019 at 10:01:01AM -0500, Patrick Hemmer
On 2019-02-01 13:30, Veiko Kukk wrote:
On 2019-02-01 12:34, Aleksandar Lazic wrote:
Do you have any errors in lighthttpds log?
Yes, it has error messages about not being enable to write to socket.
Unrecoverable error writing to socket! errno 32, retries 12, ppoll
return 1, send return
On 2019/2/14 08:20, Frederic Lecaille wrote:
> On 2/14/19 1:32 PM, Frederic Lecaille wrote:
>> On 2/13/19 7:30 PM, Patrick Hemmer wrote:
>>>
>>>
>>> On 2019/2/13 10:29, Olivier Houchard wrote:
Hi Patrick,
On Wed, Feb 13, 2019 at 10:01:01AM -0500, Patrick Hemmer wrote:
> On
On 2/14/19 1:32 PM, Frederic Lecaille wrote:
On 2/13/19 7:30 PM, Patrick Hemmer wrote:
On 2019/2/13 10:29, Olivier Houchard wrote:
Hi Patrick,
On Wed, Feb 13, 2019 at 10:01:01AM -0500, Patrick Hemmer wrote:
On 2019/2/13 09:40, Aleksandar Lazic wrote:
Am 13.02.2019 um 14:45 schrieb Patrick
On 2/13/19 7:30 PM, Patrick Hemmer wrote:
On 2019/2/13 10:29, Olivier Houchard wrote:
Hi Patrick,
On Wed, Feb 13, 2019 at 10:01:01AM -0500, Patrick Hemmer wrote:
On 2019/2/13 09:40, Aleksandar Lazic wrote:
Am 13.02.2019 um 14:45 schrieb Patrick Hemmer:
Trying to compile haproxy on my
Aleks,
Am 14.02.19 um 12:00 schrieb Aleksandar Lazic:
>> I am successfully able access brotli compressed URLs with Google Chrome,
>> this requires me to disable `gzip` though (because haproxy prefers to
>> select gzip, I suspect because `br` is last in Chrome's `Accept-Encoding`
>> header).
>
>
Hi Tim.
Am 13.02.2019 um 17:57 schrieb Tim Duesterhus:
> Willy,
> Aleks,
> List,
>
> this (absolutely non-ready-to-merge) patch adds support for brotli
> compression as suggested in issue #21:
> https://github.com/haproxy/haproxy/issues/21
Cool ;-)
> It is tested on Ubuntu Xenial with
Hi,
In our kubernetes environment, we have dynamic backend services/pods (servers)
and looking for a way in HAProxy config to resolve it through DNS resolver
config by using SNI- FQDN. Attempted below config, which parse fails due to
'%[req.ssl_sni]' in 'server' entry. Appreciate your
15 matches
Mail list logo
