Hi, all,
pidfile is handled differently in daemon mode and master-worker mode.
I added the difference to the document.
Best regards,
MIZUTA Takeshi
0001-DOC-add-description-of-pidfile-in-master-worker-mode.patch
Description: 0001-DOC-add-description-of-pidfile-in-master-worker-mode.patch
Hi,
This is a friendly bot that watches fixes pending for the next haproxy-stable
release! One such e-mail is sent periodically once patches are waiting in the
last maintenance branch, and an ideal release date is computed based on the
severity of these fixes and their merge date. Responses
On Sun, Aug 23, 2020 at 01:58:11PM +0300, gers...@gmail.com wrote:
> From: Shimi Gersner
>
> Hi Team, William,
>
> Took me some time to get back to this. This version resolves all
> comments from previous patch.
> As suggested, this is now the default behaviour.
>
> PR Reference
Hi Willy,
On Tue, Aug 25, 2020 at 14:53:05PM +0200, Willy Tarreau wrote:
> Thus an HTTP/2 request effectively "looks like" an HTTP/1 request using
> an absolute URI. What causes the mess in the logs is that such HTTP/1
> requests are rarely used (most only for proxies), but they are perfectly
>
That's improvement !
Are there similar settings in haproxy to get these numbers ?
Ionel
De: " ???"
À: "haproxy"
Envoyé: Mardi 25 Août 2020 09:25:55
Objet: [*EXT*] http/2 fine tuning
just in case someone missed
[
Willy,
Am 25.08.20 um 14:53 schrieb Willy Tarreau:
> So I think it's the right place to open such a discussion (what we should
> log and whether or not it loses info by default or requires to duplicate
> some data while waiting for the response), so that we can reach a better
> and more modern
Hi Pierre,
On Mon, Aug 24, 2020 at 08:17:05AM +, Pierre Cheynier wrote:
> On Fri, Aug 21, 2020 at 8:11 PM William Dauchy wrote:
>
> So awesome to get the first response from your direct colleague :)
>
> > I believe this is expected; this behaviour has changed since v2.1 though.
>
>
On Tue, Aug 25, 2020 at 10:23:27AM +0200, Vincent Bernat wrote:
> ? 24 août 2020 21:59 +03, Milen Simeonov:
>
> > frontend fe_main
> > bind 127.0.0.1:443 ssl crt-list /etc/haproxy/certs/websites.crt_list
>
> I am not able to reproduce. The configuration is missing a path to a
>
❦ 24 août 2020 21:59 +03, Milen Simeonov:
> frontend fe_main
> bind 127.0.0.1:443 ssl crt-list /etc/haproxy/certs/websites.crt_list
I am not able to reproduce. The configuration is missing a path to a
certificate. Does it also crash if you don't provide a crt-list?
--
Don't comment bad
just in case someone missed
https://blog.cloudflare.com/delivering-http-2-upload-speed-improvements/
10 matches
Mail list logo
