wt., 1 gru 2020 o 08:14 Willy Tarreau napisał(a):
> Ah I'm stupid, sorry! The problem is not caused by the defaults section
> but by the fact that %[path] extracts the path from the request while your
> proposal takes it from the copy of the URI that was kept for logging.
>
No need to be sorry. :
Hi,
HAProxy 2.4-dev2 was released on 2020/12/01. It added 43 new commits
after version 2.4-dev1.
Given that 2.4-dev1 experienced a few hickups, I preferred to emit a
replacement one quickly to help with testing.
We've spent more than one week dealing with races in threads and other
issues, it wa
On Tue, Dec 01, 2020 at 07:55:10AM +0100, Maciej Zdeb wrote:
> Even with mode http:
>
> defaults
> mode http
> log stdout local0
> log-format 'path:%[path]'
>
> it still fails.
>
> What is more even if you use %[path] on http frontend:
>
> defaults
> mode http
> log stdout local0
>
> frontend
Even with mode http:
defaults
mode http
log stdout local0
log-format 'path:%[path]'
it still fails.
What is more even if you use %[path] on http frontend:
defaults
mode http
log stdout local0
frontend front
mode http
# http-request set-var(txn.path) path
# log-format 'path:%[var(txn.path)]
On Tue, Dec 01, 2020 at 07:13:32AM +0100, Maciej Zdeb wrote:
> For such defaults section:
> defaults
> log stdout local0
> log-format 'path:%[path]'
>
> I'm getting following error:
> [ALERT] 335/060923 (13259) : Parsing [haproxy.cfg:11]: failed to parse
> log-format : sample fetch may not be rel
For such defaults section:
defaults
log stdout local0
log-format 'path:%[path]'
I'm getting following error:
[ALERT] 335/060923 (13259) : Parsing [haproxy.cfg:11]: failed to parse
log-format : sample fetch may not be reliably used here because it
needs 'HTTP request headers' which is not availabl
On Tue, Dec 01, 2020 at 06:54:16AM +0100, Maciej Zdeb wrote:
> There's no difference with %[path] in fact this patch only exposes "path"
> fetch as %HPR. It's only an usability matter. Usually I'm setting some sane
> log-format in the defaults section (where I can't use %[path]) and only for
> some
There's no difference with %[path] in fact this patch only exposes "path"
fetch as %HPR. It's only an usability matter. Usually I'm setting some sane
log-format in the defaults section (where I can't use %[path]) and only for
some critically important frontends I'm overwriting it to be more verbose
Hi Maciej,
On Mon, Nov 30, 2020 at 08:17:42PM +0100, Maciej Zdeb wrote:
> Hi
>
> I have a small patch which adds a new log-format variable %HPR for logging
> relative path. I hope it is clean and useful! :)
What's the difference with %[path] ? I'm trying to have a sample-fetch
equivalent for al
Good point, I just tried with boringssl and compilation failed. Thanks for
pointing that out.
On Mon, Nov 30, 2020 at 8:28 PM Илья Шипицин wrote:
> will it run on LibreSSL, BoringSSL ?
>
> вт, 1 дек. 2020 г. в 00:26, PR Bot :
>
>> Dear list!
>>
>> Author: Marcoen Hirschberg
>> Number of patches
Ilya,
Am 30.11.20 um 20:21 schrieb Илья Шипицин:
> I guess here are people running similar high density SSL hosting, do you
> have some approaches to please Chrome ? I would be happy if I can tell him
> to open separate connections for the domains that I wish.
>
Use HTTP 421 Misdirected Request:
will it run on LibreSSL, BoringSSL ?
вт, 1 дек. 2020 г. в 00:26, PR Bot :
> Dear list!
>
> Author: Marcoen Hirschberg
> Number of patches: 3
>
> This is an automated relay of the Github pull request:
>Skip unsupported ciphers for ecdsa cert
>
> Patch title(s):
>MINOR: ssl: variable renam
Dear list!
Author: Marcoen Hirschberg
Number of patches: 3
This is an automated relay of the Github pull request:
Skip unsupported ciphers for ecdsa cert
Patch title(s):
MINOR: ssl: variable renames for clarity
MINOR: ssl: skip unknown client cipher
BUG/MINOR: ssl: only choose ECDS
Hello,
I'm looking for best practices related to please Chrome on mass SSL hosting.
let us consider 3 websites
a.example.com
b.example.com
c.example.com
they share wildcard *.example.com certificate and they share single IP
address.
in such case Chrome decides to open a single http2 connectio
Hi
I have a small patch which adds a new log-format variable %HPR for logging
relative path. I hope it is clean and useful! :)
Kind regards,
czw., 26 lis 2020 o 19:08 Willy Tarreau napisał(a):
> Hi Maciej,
>
> On Thu, Nov 26, 2020 at 12:39:19PM +0100, Maciej Zdeb wrote:
> > Hi,
> >
> > Since
On Mon, Nov 30, 2020 at 07:34:51PM +0100, Tim Düsterhus wrote:
> Christopher,
> Willy,
>
> Am 30.11.20 um 18:37 schrieb Christopher Faulet:
> > Your Name (1):
> > MINOR: plock: use an ARMv8 instruction barrier for the pause
> > instruction
> >
>
> I stumbled upon that name. The commit is t
someone who wishes to stay anonymous :)
пн, 30 нояб. 2020 г. в 23:37, Tim Düsterhus :
> Christopher,
> Willy,
>
> Am 30.11.20 um 18:37 schrieb Christopher Faulet:
> > Your Name (1):
> > MINOR: plock: use an ARMv8 instruction barrier for the pause
> > instruction
> >
>
> I stumbled upon that
Christopher,
Willy,
Am 30.11.20 um 18:37 schrieb Christopher Faulet:
> Your Name (1):
> MINOR: plock: use an ARMv8 instruction barrier for the pause
> instruction
>
I stumbled upon that name. The commit is this one:
https://github.com/haproxy/haproxy/commit/1e237d037b3a45ec92d1dfa80dfd2c6b
Hi,
HAProxy 2.2.6 was released on 2020/11/30. It added 49 new commits after
version 2.2.5.
Two major bugs were fixed in this versions, both leading to a memory
corruption and random crashes. The first one was in the SPOE. Some released
spoe applets could still be referenced in the offload stream
Dear list!
Author: Thayne McCombs
Number of patches: 2
This is an automated relay of the Github pull request:
Add srvkey option to stick-table
Patch title(s):
Add srvkey option to stick-table
Harden sa2str agains 107-byte-long abstract unix domain path
Link:
https://github.com/hap
20 matches
Mail list logo
