N¬Æ§Kó0K"wë,j»÷Pý:]xÐAãPÓNûm¸ S¡h¥$Ú®·»
pµë
©®r~æ[±¢¸!jèÇ'è®h¥»++ç-n4Ñ ¨ ±ºh²ÐÚµákoLj½´×ÝtãÝ·ûM4Ð*'µéí-©à¹¨ uàÄ
íz{SÊ{¦V¢ÈZ®Ç
N¬Æ§Kó0K"wë,j¼Ô@ÂÔN5à ApÀ<`<à1ï°¢©®r~æ[±¢¸!jèÇ'è®h¥»++ç-n4Ñ
¨ ±ºh²ÐÚµäî{nj½´×Ýy×;ûM4Ð*'µéí-©à¹¨ uàÄ
íz{SÊ{¦V¢ÈZ®Ç
N¬Æ§Kó0K"wë,j¸ßÎuä>Aß~ã@µ .û ½EØÅï@Ó «îºÉ(éãj¹èë¬Þç~
ªk£ ¢¹¢ìh®Z¦º1Éú+)nÆàJæãyË@[4H*'la®,´6y;Û£¯m5÷^9ë}>ÓM4
íz{Kjx.jx1¢{^Ôò¥ë^Æß騧r«±ë
just http/1.1 enabled between
the client and haproxy. Any ideas?
Thanks,
Max
-Ursprüngliche Nachricht-
Von: Jarno Huuskonen
Gesendet: Mittwoch, 20. März 2019 12:59
An: Maximilian Böhm
Cc: haproxy@formilux.org
Betreff: Re: 400 SC on h2 xhr post
Hi Max,
On Wed, Mar 20, Maximilian B
n the client side?
Thanks,
Max
-Ursprüngliche Nachricht-
Von: Jarno Huuskonen
Gesendet: Dienstag, 19. März 2019 17:34
An: Maximilian Böhm
Cc: haproxy@formilux.org
Betreff: Re: 400 SC on h2 xhr post
Hi,
On Tue, Mar 19, Maximilian Böhm wrote:
> The problem I experience is within a le
Ursprüngliche Nachricht-
Von: Willy Tarreau
Gesendet: Dienstag, 19. März 2019 15:48
An: Maximilian Böhm
Cc: haproxy@formilux.org
Betreff: Re: 400 SC on h2 xhr post
Hi Maximilian,
On Tue, Mar 19, 2019 at 01:17:52PM +, Maximilian Böhm wrote:
> 172.17.0.1:46372 [19/Mar/2019:12:10:43.465] [fntnd
N¬Æ§Kó0K"wë,j ¹ÓQp·Ó]Ä÷ÞÂQ@Ó¯S¢©®r~æ[±¢¸!jèÇ'è®h¥»++ç-ãM
áÛk¦-
«^NçµôÆ«ÛM}×}{ço´ÓM¢{^ÒÚ ç^ @¨×§µ<©z×±·úej)Ü
ªìz
Hello,
I've setup the procedure to store and load the stats file from the socket after
a reload in order to retain the uptime of my backends.
But it actually does only retain the uptime of the frontend, backend uptime is
starting by 0s. Is it thought this way or am I doing something wrong? The
Debian (Jessie) distributes Haproxy 1.5.8.3
root@s10 # apt-get install haproxy
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
vim-haproxy haproxy-doc
The following NEW packages will be installed:
haproxy
0 upgraded, 1 newly
Thank you, Lucas, Lukas and Willy! I'll roll out the new version next year and
will (hopefully) give a better bug description next time!
Happy new year,
Max
-Ursprüngliche Nachricht-
Von: Willy Tarreau [mailto:w...@1wt.eu]
Gesendet: Samstag, 30. Dezember 2017 18:16
An:
Sorry, for my long absence. Thank you, Lucas, for perfectly describing and
digging into the issue. I'll be here if there is any further assistance
required.
Did I get it right, according to the spec, the "Connection"-header is forbidden
("MUST NOT"), still, firefox does send it? This leads
lto:ber...@luffy.cx]
Gesendet: Donnerstag, 21. Dezember 2017 11:04
An: Maximilian Böhm <maximilian.bo...@auctores.de>
Cc: haproxy@formilux.org
Betreff: Re: HTTP/2 Termination vs. Firefox Quantum
❦ 21 décembre 2017 09:00 GMT, Maximilian Böhm <maximilian.bo...@auctores.de> :
> We are
Hi there,
thanks for releasing support for http/2! Sadly, we are facing issues since
enabling it.
We are using HA-Proxy version 1.8.1-1~bpo8+1 2017/12/04 on Debian 8. On the
backend, jetty 9.3.11.v20160721 with http/1.1 answers requests.
Since I've enabled http/2 ("alpn h2,http/1.1"), we are
, it was planned to introduce the H2>H1
gateway in 1.7.
Cheers,
Max
> Am 21.11.2016 um 18:29 schrieb Lukas Tribus <lu...@gmx.net>:
>
> Hello Maximilian,
>
>
> Am 20.11.2016 um 21:13 schrieb Maximilian Böhm:
>> Hi there,
>>
>> I currently explore the poss
Hi there,
I currently explore the possibilities of HAProxy. This thing can do a lot :)
Now I’ve reached a point where I do not know what to do next. I’ve compiled
HAProxy from sources with version 1.7-dev6 (See -vv below).
The goal is to accomplish SSL/TLS bridging with some extensions as
15 matches
Mail list logo
