From: Tomas Mozes <hydrapolic@gmail.com>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] [Bugzilla] IP-based limits
Date: Fri, 14 Aug 2020 06:54:51 +0200 [thread overview]
Message-ID: <CAG6MAzS2AVKsqj9iQh=diz9p9TVBe6maDdSWQuxdrzUkA2Af2g@mail.gmail.com> (raw)
In-Reply-To: <CAAr7Pr8j+rtd-gxCUmr7fvpoQPOb+gQ7tXfxOHqxWUfspiDVug@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1107 bytes --]
On Wed, Aug 12, 2020 at 8:39 PM Alec Warner <antarus@gentoo.org> wrote:
> On Wed, Aug 12, 2020 at 11:24 AM Tomas Mozes <hydrapolic@gmail.com> wrote:
>
>>
>>
>> On Wednesday, August 12, 2020, 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.
>> > 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
>>
>> Wouldn't 429 be more appropriate?
>>
>
> The limiter doesn't support this, sorry.
>
> -A
>
>
>>
>> Tomas
>
>
It also seems that bgo loads much faster. Have any changes been done in
this direction too? Anyways, thanks!
Tomas
[-- Attachment #2: Type: text/html, Size: 2049 bytes --]
next prev parent reply other threads:[~2020-08-14 4:56 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
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 [this message]
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='CAG6MAzS2AVKsqj9iQh=diz9p9TVBe6maDdSWQuxdrzUkA2Af2g@mail.gmail.com' \
--to=hydrapolic@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