[PR] Updating Documentation for Hashing
Dear list! Author: Adam Mills Number of patches: 1 This is an automated relay of the Github pull request: Updating Documentation for Hashing Patch title(s): Updating Documentation for Hashing Link: https://github.com/haproxy/haproxy/pull/582 Edit locally: wget https://github.com/haproxy/haproxy/pull/582.patch && vi 582.patch Apply locally: curl https://github.com/haproxy/haproxy/pull/582.patch | git am - Description: Bret Mulvey, the author of the article cited in this pulication has migrated his work to papa.bretmulvey.com. I was able to view an archival version of Bret M.'s original post (http://home.comcast.net/~bretm/hash/3.html) and have validated that this is the same paper that is originally cited. Instructions: This github pull request will be closed automatically; patch should be reviewed on the haproxy mailing list (haproxy@formilux.org). Everyone is invited to comment, even the patch's author. Please keep the author and list CCed in replies. Please note that in absence of any response this pull request will be lost.
stable-bot: Bugfixes waiting for a release 2.1 (4), 2.0 (1)
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 to this mail must be sent to the mailing list. Last release 2.1.4 was issued on 2020-04-02. There are currently 4 patches in the queue cut down this way: - 4 MINOR, first one merged on 2020-04-02 Thus the computed ideal release date for 2.1.5 would be 2020-04-30, which is in two weeks or less. Last release 2.0.14 was issued on 2020-04-02. There are currently 1 patches in the queue cut down this way: - 1 MINOR, first one merged on 2020-04-02 Thus the computed ideal release date for 2.0.15 would be 2020-04-30, which is in two weeks or less. The current list of patches in the queue is: - 2.0, 2.1 - MINOR : protocol_buffer: Wrong maximum shifting. - 2.1 - MINOR : connection: always send address-less LOCAL PROXY connections - 2.1 - MINOR : ssl: memleak of the struct cert_key_and_chain - 2.1 - MINOR : ssl/cli: memory leak in 'set ssl cert' -- The haproxy stable-bot is freely provided by HAProxy Technologies to help improve the quality of each HAProxy release. If you have any issue with these emails or if you want to suggest some improvements, please post them on the list so that the solutions suiting the most users can be found.
Distance Learning Package: Bid Writing
NFP WORKSHOPS 18 Blake Street, York YO1 8QG Bid Writing Training for Charities, Schools and Public Sector Organisations. UNSUBSCRIBE To unsubscribe please reply back replacing the subject line with: REMOVE haproxy@formilux.org Unsubscribes will take effect within seven days. BID WRITING: DISTANCE LEARNING PACKAGE Learn at your home or office. No need to travel anywhere. The package includes all the topics from our popular Bid Writing: The Basics and Bid Writing: Advanced live workshops plus sample funding bids. Once you have covered all the materials you can submit up to five questions by email. TOPICS COVERED Do you know the most common reasons for rejection? Are you gathering the right evidence? Are you making the right arguments? Are you using the right terminology? Are your numbers right? Are you learning from rejections? Are you assembling the right documents? Do you know how to create a clear and concise standard funding bid? Are you communicating with people or just excluding them? Do you know your own organisation well enough? Are you thinking through your projects carefully enough? Do you know enough about your competitors? Are you answering the questions funders will ask themselves about your application? Are you submitting applications correctly? Are you applying to the right trusts? Are you applying to enough trusts? Are you asking for the right amount of money? Are you applying in the right ways? Are your projects the most fundable projects? Are you carrying out trust fundraising in a professional way? Are you delegating enough work? Are you highly productive or just very busy? Are you looking for trusts in all the right places? How do you compare with your competitors for funding? Is the rest of your fundraising hampering your bids to trusts? Do you understand what trusts are ideally looking for? TRAINEES Staff members, volunteers, trustees or board members of charities, schools or public sector organisations who intend to submit grant funding applications to charitable grant making trusts and foundations. People who provide advice to these organisations may also order. ORDER YOUR PACKAGE NOW The cost of the Bid Writing: Distance Learning Package is £190 per trainee. To order please reply back replacing the subject line with: ORDER Please tell us: 1) The name of the trainee. 2) The email address to send the materials to. 3) The name of your organisation. 4) The postal address of your organisation. 5) A purchase order number if required. We will send you an invoice within 24 hours containing BACS electronic payment details. Once we receive payment the materials will be emailed to the specifed email address within 24 hours. Please check your spam folder to ensure you receive everything. TERMS Training materials are for use only by the trainee named on the invoice. Training materials may not be copied, circulated or published. QUESTIONS If you have a question please reply back replacing the subject line with: QUESTION
Re: TLV problem after updating to 2.1.14
On Tue, Apr 14, 2020 at 05:18:39PM +0500, ??? wrote: > besides junk food, are you ok? Yes, it's just that my mood varies a lot from day to day :-/ We still have *at least* 4 weeks so stand that. It's the first time they dare announcing a possible start of the end. We'll see. These health check details aside, I've pushed the cleaned up version of the fix to the master and 2.1 branches so that Hativ doesn't need to maintain a local patch anymore. Cheers, Willy
Re: TLV problem after updating to 2.1.14
вс, 12 апр. 2020 г. в 21:22, Willy Tarreau :
> Hello Hativ,
>
> On Sun, Apr 12, 2020 at 09:49:02AM +0200, Hativ wrote:
> > Hello Willy,
> > > Hativ, if I send you a patch to test next week, is it possible to
> > > give
> > > it a try on your side ? I'm interested in knowing if a clean "LOCAL"
> > > connection works fine with Dovecot. If so then in parallel we can
> > > file
> > > a report on Dovecot to make their parser more robust but at least
> > > we'd
> > > have a longterm solution that doesn't affect deployed servers.
> >
> > I didn't get a patch so far.
>
> I'm really sorry for this. It just turns out that having been enclosed for
> 4 weeks eating only junk food starts to seriously challenge my ability to
> concentrate on any work and stay focused more than five seconds... and the
> total lack of perspectives of any imminent improvement of this painful
> situation definitely does not help :-(
>
besides junk food, are you ok?
>
> Here comes a patch (copy-pasted, you just have to copy that new line).
> It's not the final one, because if it works, then we'll also need to
> remoe the unused local-specific parts from the "else" block, but that's
> a pure detail for now.
>
> Thanks,
> Willy
>
> diff --git a/src/connection.c b/src/connection.c
> index 5a2fd95bc2..0bafcdb919 100644
> --- a/src/connection.c
> +++ b/src/connection.c
> @@ -1378,6 +1378,7 @@ int make_proxy_line_v2(char *buf, int buf_len,
> struct server *srv, struct connec
> /* At least one of src or dst is not of AF_INET or AF_INET6 */
> if ( !src
>|| !dst
> + || conn_is_back(remote)
>|| (src->ss_family != AF_INET && src->ss_family != AF_INET6)
>|| (dst->ss_family != AF_INET && dst->ss_family != AF_INET6)) {
> if (buf_len < PP2_HDR_LEN_UNSPEC)
>
>
>
>
Re: Question regarding increasing requests more than 32kb
Hi Aravind. On 14.04.20 06:42, Aravind Viswanathan wrote: Hi Alek, Thanks for the response. Could you please let me know if these parameters need to be set on Global or Defaults section? Please be so kind and read the documentation there is shown in which section this parameter have to be set, because it's not just set a parameter. I strongly recommend to understand what this parameter do, which impact it have and why it's in the specific section. Regards, Aravind Viswanathan -Original Message- From: Aleksandar Lazic Sent: Monday, April 13, 2020 4:14 PM To: Aravind Viswanathan Cc: haproxy@formilux.org Subject: Re: Question regarding increasing requests more than 32kb Hi. On 13.04.20 08:18, Aravind Viswanathan wrote: Hi Team, Good Morning. We are using HaProxy as a load balancer in our bitbucket system and Bitbucket is linked to JIRA via Application links. Please can you share the haproxy version and your config. haproxy -vv Recently we noticed an error in our JIRA log 2020-04-01 03:08:23,477 Caesium-1-3 ERROR ServiceRunner [c.a.j.p.devstatus.provider.DefaultDevSummaryPollService] Refresh failure com.atlassian.jira.plugin.devstatus.provider.DataProviderRefreshFailure: Data Provider refresh failed with error code 400 and message - HTTP status 400 Bad request] and when we checked the same with Atlassian support they said we need to configure request going through HAProxy is allowed as big as 32kb. I thought Increasing the maxconn might solve this but later I understood, maxconn Sets the maximum per-process number of concurrent connections to . Could you please advise how to configure request going through HAProxy is allowed as big as 32kb? You could take a look to this parameter which describes the correlation between tune.bufsize, tune.maxrewrite and maxconn. https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcbonte.github.io%2Fhaproxy-dconv%2F2.1%2Fconfiguration.html%23tune.bufsizedata=02%7C01%7CAravind.Viswanathan%40efi.com%7C01112b41876642f7c4bc08d7df97a09c%7C3fe4532499b245c397517034bae71475%7C0%7C0%7C637223714645124453sdata=miZ7S%2FByUOE00tsvHLDzeMNgY1CBRagyQmFKhqYfhgc%3Dreserved=0 /Regards,/ /Aravind Viswanathan/ Confidentiality notice: This message may contain confidential information. It is intended only for the person to whom it is addressed. If you are not that person, you should not use this message. We request that you notify us by replying to this message, and then delete all copies including any contained in your reply. Thank you. Again a useless text as you send the Mail to a public mailing list. https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FEmail_disclaimerdata=02%7C01%7CAravind.Viswanathan%40efi.com%7C01112b41876642f7c4bc08d7df97a09c%7C3fe4532499b245c397517034bae71475%7C0%7C0%7C637223714645124453sdata=JoLQJJ6ArmUC7jAT%2BDTMGtHINcnhHVV0QO%2FSW1z%2BVco%3Dreserved=0 Regards Aleks
