son schema.
However, it seems that the currently generated schema is not valid, at
least by checking on this website :
https://www.jsonschemavalidator.net/
Is the json schema useful to anyone or can I safely ignore/remove it ?
Thanks for your feedback,
--
Amaury Denoyelle
't worry :-)
At the moment I'm always interested to add simple feature, but I also
would like to progress with my patch serie on stats so I'm not sure if I
will have the time for this :/
--
Amaury Denoyelle
fects are quickly
> tested.
FIY, I have looked upon the issue and seems to have now a working
implementation. I will probably be able to produce a clean patch soon.
--
Amaury Denoyelle
he backports for haproxy 1.8, I will try to make a
release with your fix soon.
--
Amaury Denoyelle
e that in absence of any response this
>pull request will be lost.
I can reproduce your issue on haproxy master. However I'm not sure why
idle_conns list is NULL in this case so I'll investigate it before
validating your patch.
--
Amaury Denoyelle
xy-1.8.git/
Git Web browsing : http://git.haproxy.org/?p=haproxy-1.8.git
Changelog: http://www.haproxy.org/download/1.8/src/CHANGELOG
Cyril's HTML doc : http://cbonte.github.io/haproxy-dconv/
---
Complete changelog :
Amaury Denoyelle (6):
BUG/MINOR: config: Fix memory leak on co
of my
implementation is less surprising, but if it is a real use-case, I do
not want to break it without knowing it.
Let me know if I'm not clear,
I'm putting the list on copy in case someone has an opinion on the
subject.
Thank you for your help,
--
Amaury Denoyelle
Tim Düsterhus wrote:
> Amaury,
> Am 21.01.21 um 16:40 schrieb (Amaury Denoyelle):
> > I have a question for you on the case of the proxy protocol. One of
> > these special parameters to identify a connection is the content of the
> > proxy protocol block. However, this
://www.haproxy.org/download/1.8/src/CHANGELOG
Cyril's HTML doc : http://cbonte.github.io/haproxy-dconv/
Amaury Denoyelle
---
Complete changelog :
Amaury Denoyelle (2):
BUG/MINOR: config: copy extra cookie attributes from dfl proxy
BUG/MINOR: srv: do not init address if backend is disabled
ow if the restart is systemd’s
> action).
> Any idea about what could we do?
> Thank you very much in advance!
> Oriol
> P.S. I don’t attach logs or system config to keep this first post simple,
> but if anyone wants to give them a look I’ll be happy to share; so just
> a
ase, but things are
> looking good and I don't expect to have to come back here crying.
> So thank you very much for your help!
Great news ! I will merge the fix soon in the dev branch and it should
hit the next serie of stable releases. Thank you again for your report
and your feedback.
--
Amaury Denoyelle
://git.haproxy.org/?p=haproxy-1.8.git
Changelog: http://www.haproxy.org/download/1.8/src/CHANGELOG
Cyril's HTML doc : http://cbonte.github.io/haproxy-dconv/
---
Complete changelog :
Amaury Denoyelle (2):
BUG/MINOR: config: fix leak on proxy.conn_src.bind_hdr_name
CLEANUP: remove
/download/2.0/src/
Git repository : http://git.haproxy.org/git/haproxy-2.0.git/
Git Web browsing : http://git.haproxy.org/?p=haproxy-2.0.git
Changelog: http://www.haproxy.org/download/2.0/src/CHANGELOG
Cyril's HTML doc : http://cbonte.github.io/haproxy-dconv/
Amaury Denoyelle
://cbonte.github.io/haproxy-dconv/
Amaury Denoyelle
---
Complete changelog :
Willy Tarreau (8):
MINOR: time: also provide a global, monotonic global_now_ms timer
BUG/MEDIUM: freq_ctr/threads: use the global_now_ms variable
BUG/MEDIUM: time: make sure to always initialize the global tick
Hi,
I will try to emit new releases next week for 2.0 and 1.8 which are
impacted by the bug you mentionned.
--
Amaury Denoyelle
On Wed, Oct 20, 2021 at 07:03:43PM +0100, David CARLIER wrote:
> Hi
> here a little patch for netbsd system.
> Kind regards.
Thanks, I'm currently trying to fix other issues with NetBSD9.2, so I'll
merge your patch with my work.
--
Amaury Denoyelle
est to better
handle h2 websocket.
Regards,
--
Amaury Denoyelle
repository : http://git.haproxy.org/git/haproxy-2.0.git/
Git Web browsing : http://git.haproxy.org/?p=haproxy-2.0.git
Changelog: http://www.haproxy.org/download/2.0/src/CHANGELOG
Cyril's HTML doc : http://cbonte.github.io/haproxy-dconv/
---
Complete changelog :
Amaury Denoyelle (1):
erver'
> srv->ssl_ctx.alpn_len);
> ~~~ ^
> Version 2.4.8 builds fine.
>
>
Thanks for your report. One of my commit to handle properly websocket on
the server side introduces this issue. I'm working on a fix.
--
Amaury Denoyelle
p the patches in your tree so we can have a more substantial
list of change for a new version ?
--
Amaury Denoyelle
quot;${HOME}/opt" --openssldir="${HOME}/opt"
> --libdir=lib -DPURIFY
> +make -j$(nproc) build_sw
> +make install_sw
> +
> +)
> +fi
> --
> 2.29.2.windows.2
>
Thank you for your patches. However, we should probably fix the GCC
error reproduced on your repository before merging it. This will prevent
to have a red test indicator indefinitely.
--
Amaury Denoyelle
On Sat, Oct 30, 2021 at 12:25:13PM +0100, David CARLIER wrote:
> Hi here a patch to address freebsd build failure.
> Kind regards.
Thanks, applied.
--
Amaury Denoyelle
oon as possible.
--
Amaury Denoyelle
t; Regards.
I have merged your patch, thanks for your contribution. Note that I have
splitted it in two to facilitate possible revert or cherry-picking of
numa_detect_topology() various implementation. I also used the BUG_ON
macro which is the idiomatic way for asserts in haproxy.
Sorry for the delay, and thanks again,
--
Amaury Denoyelle
> file...
> --
> Christopher Faulet
>
To add more context on this discussion, I looked at dynamic servers.
Currently, the behavior is identical with the configuration as
init_srv_check() is used in the "add server" CLI handler. This is really
problematic as "no-check-ssl" is not available for dynamic servers, so
if I understand correctly it's not possible to add a dynamic SSL server
with checks on the same port without SSL on checks.
Christopher's patch for init_srv_check() is probably a good idea, but if
not taken it should be probably at least used for servers with the
SRV_F_DYNAMIC flag.
--
Amaury Denoyelle
d debug options
to be able to quickly understand bugs, so this may have an impact on the
results of perfs test.
Now, we are focused on trying to deploy QUIC on haproxy.org to inspect
the behavior with real-life browsers. When this is done, the next
objective will be to try to improve the results of these perfs tests.
--
Amaury Denoyelle
your process.
Thanks again for your help,
Regards,
--
Amaury Denoyelle
On Tue, Apr 12, 2022 at 05:26:41PM +0200, Amaury Denoyelle wrote:
> On Tue, Apr 12, 2022 at 08:01:59AM -0600, Shawn Heisey wrote:
> > On 4/12/22 02:22, Amaury Denoyelle wrote:
> > > then you can display the traces with the following command :
> > > $ show events bu
On Tue, Apr 12, 2022 at 08:01:59AM -0600, Shawn Heisey wrote:
> On 4/12/22 02:22, Amaury Denoyelle wrote:
> > then you can display the traces with the following command :
> > $ show events buf0
> > > For the h3 layer, the trace mechanism is not currently implemented
On Tue, Apr 12, 2022 at 10:30:05AM -0600, Shawn Heisey wrote:
> On 4/12/22 09:45, Amaury Denoyelle wrote:
> > After much analysis of the code, it may be useful to have a run with the
> > stream traces as well :
> > $ trace stream sink buf0; trace stream level developer; trace
On Wed, Apr 13, 2022 at 10:36:00AM +0200, Amaury Denoyelle wrote:
> On Tue, Apr 12, 2022 at 10:30:05AM -0600, Shawn Heisey wrote:
> > On 4/12/22 09:45, Amaury Denoyelle wrote:
> > > After much analysis of the code, it may be useful to have a run with the
> > > stream tra
On Wed, Apr 13, 2022 at 08:16:06AM -0600, Shawn Heisey wrote:
> On 4/13/22 02:42, Amaury Denoyelle wrote:
> > Ok this seems related to 'option abortonclose'. Without this, I do not
> > have a 400 error. Can you confirm me this behavior on your side please ?
>
> If I remove t
On Thu, Apr 14, 2022 at 07:29:20AM -0600, Shawn Heisey wrote:
> On 4/14/22 03:27, Amaury Denoyelle wrote:
> > So to summary, this option should be activated if you only have browsers
> > as client and the traffic is big enough to saturate haproxy queues.
> > I hope this will
ection dedicated socket instead.
The socket fallback has been implemented silently first as on some
platform it may not be supported at all. We plan to change this soon to
report a log on the first permission error to improve the current
situation.
Hope this helps,
--
Amaury Denoyelle
liment for haproxy reliability. We hope one day
we will reach this level for QUIC but for now this objectif is still
far.
--
Amaury Denoyelle
like you did not run the correct binary as
this does not corresponds to the version reported by -vv. Have you
ensure to run the binary directly on the command-line using an absolute
path ?
--
Amaury Denoyelle
handle all the cases. Sadly, this
requires some reflexion time and it won't be solve before the imminent
2.6 release. For the moment, you can try on your side to
increase/decrease the haproxy client timeout to see if this change your
situation.
Regards,
--
Amaury Denoyelle
alloc(global.nbthread,
> + sizeof(*quic_accept_queues));
> if (!quic_accept_queues) {
> ha_alert("Failed to allocate the quic accept queues.\n");
> return 0;
> --
> 2.36.1
>
Fine for me,
Thanks,
--
Amaury Denoyelle
roxy.org/l/pending-bugs
Reviewed bugs: http://www.haproxy.org/l/reviewed-bugs
Code reports : http://www.haproxy.org/l/code-reports
Latest builds: http://www.haproxy.org/l/dev-packages
---
Complete changelog :
Amaury Denoyelle (10):
BUG/MINOR: h3: fix frame type defin
QUIC issues resolved so far.
Regards,
--
Amaury Denoyelle
but it could be extended
easily, for example to differentiate between CLI and Lua
interactions.
3. Should we aim to always print stderr logs also on the CLI output ?
This could be useful to return more details on the cause of success
or error.
Ideally, we should decide on this before the next 2.7 release.
Thanks everyone for your feedback,
--
Amaury Denoyelle
php code.
> https://http3test.elyograg.org/
Thank you very much for your kind words and your first reports on QUIC
which have greatly helped us. Let's hope we keep refine QUIC support
even more in the near future.
--
Amaury Denoyelle
interested
> in giving 2.8-dev1 a try, it would confirm whether you're facing this
> exact issue. But at the moment we're not aware of any remaining crash-
> inducing bugs in 2.8-dev, so if it would still fail for you it would
> indicate a new unknown bug.
Luke, the crashes you reporte
On Thu, Dec 15, 2022 at 09:20:01AM +0100, Amaury Denoyelle wrote:
> On Thu, Dec 15, 2022 at 09:03:18AM +0100, Amaury Denoyelle wrote:
> > On Thu, Dec 15, 2022 at 08:58:16AM +0100, Amaury Denoyelle wrote:
> > > On Wed, Dec 14, 2022 at 11:20:44PM -0700, Shawn Heisey wrote:
> &g
On Thu, Dec 15, 2022 at 09:03:18AM +0100, Amaury Denoyelle wrote:
> On Thu, Dec 15, 2022 at 08:58:16AM +0100, Amaury Denoyelle wrote:
> > On Wed, Dec 14, 2022 at 11:20:44PM -0700, Shawn Heisey wrote:
> > > On 12/14/22 21:23, Илья Шипицин wrote:
> > > > Can you try to
On Thu, Dec 15, 2022 at 08:58:16AM +0100, Amaury Denoyelle wrote:
> On Wed, Dec 14, 2022 at 11:20:44PM -0700, Shawn Heisey wrote:
> > On 12/14/22 21:23, Илья Шипицин wrote:
> > > Can you try to bisect?
> > I had made some incorrect assumptions about what's needed to use
&g
ular reloads as a way of resetting what
> the browser remembers. That seems to work.
> The bisect process only took a few runs to find the problem commit:
> 3ca4223c5e1f18a19dc93b0b09ffdbd295554d46 is the first bad commit
> commit 3ca4223c5e1f18a19dc93b0b09ffdbd295554d46
> Author: Ama
ot;, tp->coosen);
chooen instead of chosen :
-/* Encode version information transport parameters with as
choosen
+/* Encode version information transport parameters with as
chosen
With this adjusted it compiled. I'm definitely ok with spelling patch
but you should at least try to compile it before submitting because it's
pretty easy to miss errors on this kind of fix. Anyway thanks for your
help.
--
Amaury Denoyelle
your problem
is probably not related to haproxy retries.
--
Amaury Denoyelle
On Fri, Mar 03, 2023 at 09:35:45AM +0100, Jack Bauer wrote:
> Am Do., 2. März 2023 um 17:52 Uhr schrieb Amaury Denoyelle <
> adenoye...@haproxy.com>:
> >
> > It seems you do not use 'option redispatch' in your configuration so a
> > retry will never be conducted on a
LI_F_QUIC_LISTENER flag
--
Amaury Denoyelle
: https://www.haproxy.org/l/code-reports
Latest builds: https://www.haproxy.org/l/dev-packages
---
Complete changelog :
Amaury Denoyelle (13):
BUG/MINOR: quic: wake up MUX on probing only for 01RTT
BUG/MINOR: quic: ignore congestion window on probing for MUX wakeup
BUG
---
Complete changelog :
Amaury Denoyelle (5):
BUG/MINOR: quic: wake up MUX on probing only for 01RTT
BUG/MINOR: trace: fix hardcoded level for TRACE_PRINTF
BUG/MEDIUM: mux-quic: release data from conn flow-control on qcs reset
BUG/MINOR: h3: properly handle incomplete
/haproxy/commit/511ddd5785266c149dfa593582512239480e1688
> I can fill a "bug" report on github if necessary.
Indeed good catch.
If you have the time, can you provide us a proper patch for this ? There
is some insight in the CONTRIBUTING file for this. If not, I will submit
the change myself.
--
Amaury Denoyelle
l body so I integrated it directly into the patch.
As for backport information, most of the time we skip documentation
patches when they are only for spelling fixes. However as this one is
directly to correct a referenced keyword we may choose to backport it.
--
Amaury Denoyelle
quic.conn-owner.
Merged, thank you very much !
Do not hesitate to give us feedback if you test QUIC support :)
--
Amaury Denoyelle
rendered doc output that keywords in
the "See also" section are not highlighted with a link. Maybe because
quotes are missing around.
Regards,
--
Amaury Denoyelle
r (this is on an Ubuntu 22.04 server)
Alas for the moment HTTP/3 upload are limited indeed by the flow control
which is equivalent to tune.bufsize. To remove this limitation, I wish
to implement a multi-buffer receive per stream, but for now this is not
yet planned.
--
Amaury Denoyelle
figuration file
servers. In particular, I do not know how we should handled duplicate
cookie values in this case.
--
Amaury Denoyelle
il when we reach this:
>* publishing EVENT_HDL_SUB_SERVER_ADD
>*/
> --
> 2.34.1
>
Thank you very much. This was merged in our development tree. In the
meantime, I also enabled "cookie" keyword for dynamic servers as nothing
prevented it.
--
Amaury Denoyelle
On Fri, Mar 22, 2024 at 09:45:59AM +, Damien Claisse wrote:
> Hi Amaury!
> Sorry for the HTML message, I have to use a *** well-known enterprise MUA :(
> Le 22/03/2024 09:09, « Amaury Denoyelle » a écrit :
>> This patch raises several interrogations. First, dynamic servers a
) instead,
> it will only report this when starting with -dD (config diagnostic mode).
I have a doubt though, will this kind of configuration really works ? I
though that for the moment if name parameter is specified, it is
mandatory to use a server with SSL+SNI.
--
Amaury Denoyelle
62 matches
Mail list logo
