From: Raymond Jennings <shentino@gmail.com>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] [Bugzilla] IP-based limits
Date: Wed, 12 Aug 2020 09:40:13 -0700 [thread overview]
Message-ID: <CAGDaZ_py8CLh_7Ac-qe55P+LRBXbS32ZzZw-jO3zK=JF5e23Rw@mail.gmail.com> (raw)
In-Reply-To: <CAAr7Pr8UgVQXerbA7EDvrS8fa3qkcGEg+6X7o-XBkQ_kBk+SJA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 927 bytes --]
On Wed, Aug 12, 2020 at 8:58 AM Alec Warner <antarus@gentoo.org> wrote:
> Bugzilla now has connection limits per IP. I won't say what the limit is,
> but if you are crawling bugzilla or using automated tools from a single
> source IP you may hit the limit and receive 503's for requests over the
> limit.
>
I haven't had a chance to test this for myself but do the 503 messages give
any indication as to the IP limit being WHY the 503's are being returned or
was this change made/option provided upstream by bugzilla's maintainers?
This may be a particular problem for users behind things like carrier grade
> NAT (where many users are multiplexed through a single egress IP.) However
> we have seen numerous slowdowns from bot traffic and this is a relatively
> straightforward change to make on our end. If you believe you are being
> unfairly limited / blocked, please reach out to infra@gentoo.org.
>
> Thanks,
>
> -A
>
[-- Attachment #2: Type: text/html, Size: 1487 bytes --]
next prev parent reply other threads:[~2020-08-12 16:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-12 15:58 [gentoo-project] [Bugzilla] IP-based limits Alec Warner
2020-08-12 16:40 ` Raymond Jennings [this message]
2020-08-12 18:23 ` Tomas Mozes
2020-08-12 18:37 ` Raymond Jennings
2020-08-12 18:39 ` Alec Warner
2020-08-12 18:43 ` Raymond Jennings
2020-08-12 19:10 ` Alec Warner
2020-08-14 4:54 ` Tomas Mozes
2020-08-14 7:07 ` Alec Warner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGDaZ_py8CLh_7Ac-qe55P+LRBXbS32ZzZw-jO3zK=JF5e23Rw@mail.gmail.com' \
--to=shentino@gmail.com \
--cc=gentoo-project@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox