Re: [PATCH] DOC: Fix formatting in configuration.txt to fix dconv
On Fri, May 27, 2022 at 11:20:36PM +0200, Tim Duesterhus wrote: > The missing space before the colon causes haproxy-dconv to misparse the > configuration.txt. Thanks Tim, now merged. Willy
[PATCH] DOC: Fix formatting in configuration.txt to fix dconv
The missing space before the colon causes haproxy-dconv to misparse the configuration.txt. --- doc/configuration.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/configuration.txt b/doc/configuration.txt index 3a5728539..6343f9f13 100644 --- a/doc/configuration.txt +++ b/doc/configuration.txt @@ -18126,7 +18126,7 @@ ipv4() : ipv4 ipv6() : ipv6 Returns an ipv6. -last_rule_file: string +last_rule_file : string This returns the name of the configuration file containing the last final rule that was matched during stream analysis. A final rule is one that terminates the evaluation of the rule set (like an "accept", "deny" or @@ -18140,7 +18140,7 @@ last_rule_file: string logs where was the rule that gave the final verdict, in order to help figure why a request was denied for example. See also "last_rule_line". -last_rule_line: integer +last_rule_line : integer This returns the line number in the configuration file where is located the last final rule that was matched during stream analysis. A final rule is one that terminates the evaluation of the rule set (like an "accept", "deny" or -- 2.36.1
Quote Request
Greetings, I would like to be furnished with detailed information on availability, price and method of payment of the below Ubiquiti. Ubiquiti Networks UAP-AC-LITE wireless access point 1000 Mbit/s White Power over Ethernet (PoE) (UAP-AC-LITE) Ubiquiti UAP-AC-M-PRO-US AP Ubiquiti Nanostation NSM5, 5GHz, 802.11a/n Hi-power 20 dBm Minimum, 2x2 MIMO AirMax TDMA PoE Station Brian Gasser Axcent Technology Purchase Manager 773-943-3423 axcenttechnol...@gmail.com
[ANNOUNCE] haproxy-2.6-dev12
Hi, HAProxy 2.6-dev12 was released on 2022/05/27. It added 149 new commits after version 2.6-dev11. Yeah I know, I said we'll only issue -dev12 if we face some trouble. But stay cool, we didn't face any trouble. However we figured that it would help last-minute testers to have a final tagged version. The vast majority of patches are tagged CLEANUP and MINOR. That's great. One old github issue was finally addressed, regarding the HTTP version validation. In the past we used to accept any 4-letter protocol using letters H,P,R,S,T, which allowed us to match both HTTP and RTSP. But it was reported to cause trouble because it was neither possible to disable RTSP support not extend this to other protocols. The problem with having RTSP enabled by default is that if haproxy forwards it to a backend server that doesn't know it, the server may respond with an HTTP/0.9 error that will be blocked by haproxy which then returns a 502 error. That's no big deal until you're watching your load balancer's logs and counters. So now by default only HTTP is accepted, and this can be relaxed by adding "accept-invalid-http-request". To be honest, I really doubt that there are that many people using RTSP, given that we never ever get any single problem report about it, so I think it will not be a big deal to add this option in such cases so that all other users gain in serenity. This will likely be backported but if so, very slowly as this will be a behavior change, albeit a very small one. Some polishing was done on QUIC, to improve the behavior on closing connections and stopping the process, and error processing in general. The maintainability was also improved by refactoring certain areas. Ah, crap, I just noticed that we missed a few patches from Fred who added some doc and a few settings! The conn_streams that were holding up the release are now gone. It took two of us two full days of code analysis and head scratching to figure the role of certain antique flags and give them a more appropriate name, but that was really necessary. I must admit I really like the new model in 2.6, it's much more consistent and logical than 2.5 and older. It's visible in that it's easier to document and explain. And even during the changes it was easier to figure the field names for parts that had to be changed manually. There are a bit more patches than I initially expected because this time I refused to leave poorly named function arguments and local variables: we've suffered from this for many years where process_stream() used to have a "struct stream *sess" and the session was "sess->sess". I didn't want to experience this anymore, we need the code to be more intuitive and readable especially for new contributors, and given the large amount of changes since 2.5 that will complicate backports anyway, it was the perfect opportunity to pursue that quest. While these changes represent many patches, they're essentially renames. There's always the tiny risk of an undetected mistake but all of them are trivial, were reviewed multiple times, built and individually tested so I'm not worried (famous last words :-)). Some of us will continue testing over the week-end (it's already deployed on haproxy.org). I think we'll add a few bits of doc, Fred's patches that we missed, maybe a fix or two for last minute issues, and I expect to release on Tuesday (because Mondays are usually too short). Please find the usual URLs below : Site index : http://www.haproxy.org/ Documentation: http://docs.haproxy.org/ Wiki : https://github.com/haproxy/wiki/wiki Discourse: http://discourse.haproxy.org/ Slack channel: https://slack.haproxy.org/ Issue tracker: https://github.com/haproxy/haproxy/issues Sources : http://www.haproxy.org/download/2.6/src/ Git repository : http://git.haproxy.org/git/haproxy.git/ Git Web browsing : http://git.haproxy.org/?p=haproxy.git Changelog: http://www.haproxy.org/download/2.6/src/CHANGELOG Pending bugs : http://www.haproxy.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 Willy --- Complete changelog : Amaury Denoyelle (26): BUG/MEDIUM: mux-quic: adjust buggy proxy closing support Revert "MINOR: quic: activate QUIC traces at compilation" Revert "MINOR: mux-quic: activate qmux traces on stdout via macro" MINOR: h3: mark ncbuf as const on h3_b_dup MINOR: mux-quic: do not alloc quic_stream_desc for uni remote stream MINOR: mux-quic: delay cs_endpoint allocation MINOR: mux-quic: add traces in qc_recv() MINOR: mux-quic: adjust return value of decode_qcs CLEANUP: h3: rename struct h3 -> h3c CLEANUP: h3: rename uni stream type constants BUG/MINOR: h3: prevent overflow when parsing SETTINGS MINOR: h3: refactor
Re: [PATCH] BUG/MEDIUM: sample: Fix adjusting size in word converter
On Wed, May 25, 2022 at 10:58:51PM -0600, astrotha...@gmail.com wrote: > From: Thayne McCombs > > Adjust the size of the sample buffer before we change the "area" > pointer. Otherwise, we end up not changing the size, because the area > pointer is already the same as "start" before we compute the difference > between the two. > > This is similar to the change in b28430591d18f7fda5bac2e0ea590b3a34f04601 > but for the word converter instead of field. Good catch, now merged, thank you Thayne! Willy
Re: [PATCH] REGTESTS: Do not use REQUIRE_VERSION for HAProxy 2.5+ (2)
On Mon, May 23, 2022 at 10:45:36PM +0200, Tim Duesterhus wrote: > Introduced in: > > 18c13d3bd MEDIUM: http-ana: Add a proxy option to restrict chars in request > header names (...) Merged, thanks Tim! Willy
Barclay finanse
Ponieważ zauważyliśmy duże zainteresowanie pozyskaniem kapitału, pragniemy poinformować o nowych instrumentach finansowych oraz alternatywnych żródlach finansowania przedsiębiorstw. Finansowanie od 1 mln złotych . Aby uzyskać bezpłatną informację w zakresie pozyskania finansowania dla swojej firmy prosimy o podanie numeru telefonu do osoby odpowiedzialnej za kapitał. Departament ds. Finansowania Przedsiębiorstw Barclay Financial Group Sp. z o.o. Warsaw Trade Tower Ul. Chłodna 51, 36 piętro 00-867 Warszawa, Polska Tel kom : 781 607 111 Tel stacj: +48 (22) 223 05 18 www.barclay.com.pl e- mail: bi...@barclay.com.pl -- Ta wiadomość e-mail została sprawdzona pod kątem wirusów przez oprogramowanie AVG. http://www.avg.com
Re: how to install on RHEL7 and 8
good news :) I found some time to dig in into IUS. I'm playing with builds (something works, something not yet, but I'm progressing). hopefully, we will end with owning IUS repos and/or making PRs. чт, 26 мая 2022 г. в 16:08, William Lallemand : > Ilya, > > On Thu, May 26, 2022 at 03:13:54PM +0500, Илья Шипицин wrote: > > I'll try to focus on redhat packaging (I'm somewhat familiar with Fedora > > COPR, and I can try OBS). > > > > I don't think OBS is relevant for this case, the documentation is poor > and it's complicated to contribute to a package. > > I don't know about COPR, but most of the work seems to have been done in > IUS, and it's easy to contribute just by doing a pull request on their > repository. I'm not sure there is any advantage to creating another > repository, but I might be wrong. > > > > if I will not come back in next couple of weeks, that means I did not > find > > a time. > > > > Well be careful then, because I'm talking about long-term maintenance, > not just another package not being updated after a few months like all > haproxy RPM that we can find out there. It really takes time and > dedication. > > Regards, > > -- > William Lallemand >
Re: how to install on RHEL7 and 8
On 2022-05-26 20:28, Ryan O'Hara wrote: On Wed, May 25, 2022 at 11:15 AM William Lallemand wrote: On Tue, May 24, 2022 at 08:56:14PM +, Alford, Mark wrote: Do you have instruction on the exact library needed to fo the full install on RHEL 7 and RHEL 8 I read the INSTALL doc in the tar ball and the did the make command and it failed because of LUA but lua.2.5.3 is installed Please help Hello, I'm using this thread to launch a call for help about the redhat packaging. I am the maintainer for all the Red Hat and Fedora packages. Feel free to ask questions here on the mailing list or email me directly. We try to document the list of available packages here: https://github.com/haproxy/wiki/wiki/Packages The IUS repository is know to work but only provides packages as far as 2.2. no 2.3, 2.4 or 2.5 are there but I'm seeing an open ticket for the 2.4 here: https://github.com/iusrepo/wishlist/issues/303 Unfortunately nobody ever step up to maintain constantly the upstream releases for redhat/centos like its done for ubuntu/debian on haproxy.debian.net [1]. I try to keep Fedora up to date with latest upstream, but once a release goes into a specific Fedora release (eg. haproxy-2.4 in Fedora 35) I don't update to haproxy-2.5 in that same release. I have in the past and I get angry emails about rebasing to a newer release. I've spoken to Willy about this in the past and we seem to be in agreement on this. RHEL is different. We almost never rebase to a later major release for the lifetime of RHEL. The one exception was when we added haproxy-1.8 to RHSCL (software collections) in RHEL7 since the base RHEL7 had haproxy-1.5 and there were significant features added to the 1.8 release. I get this complaint often for haproxy in RHEL. Keep in mind that RHEL is focused on consistency and stability over a long period of time. I can't stress this enough - it is extremely rare to rebase to a new, major release of haproxy (or anything else) in a major RHEL release. For example, RHEL9 has haproxy-2.4 and will likely always have that version. I do often rebase to newer minor release to pick up bug fixes (eg. haproxy-2.4.8 will be updated to haproxy-2.4.17, but very unlikely to be anything beyond the latest 2.4 release). I understand this is not for everybody. IMHO, if you pick a LTS or even a non-LTS (depending on how long the distro version ist being supported) but keep that close to upstream releases by doing minor bumps, that's totally fine. That way, like you said, users get bug fixes and not just hand picked patches. That's far better I'd say. Maybe it could be done with IUS, its as simple as a pull request on their github for each new release, but someone need to be involve. I'm not a redhat user, but from time to time someone is asking for a redhat package and nothing is really available and maintained outside of the official redhat one. As mentioned elsewhere, COPR is likely the best place for this. It had been awhile since I've used it, but there have been times I did special, unsupported builds in COPR for others to use. Hope this helps. Ryan Links: -- [1] http://haproxy.debian.net -- Regards, Christian Ruppert
