From: Slavko <linux@slavino.sk>
To: netfilter@vger.kernel.org
Subject: Re: Bot protection on RSS feed for git.netfilter.org
Date: Mon, 20 Jul 2026 20:13:45 +0200 [thread overview]
Message-ID: <20260720201345.51e926cf@bonifac.skk> (raw)
In-Reply-To: <178456987406.6.15350942097428291948.1495131021@simplelogin.com>
Ahoj,
Dňa Mon, 20 Jul 2026 17:51:05 +0000 netfilter.btvdk@simplelogin.com
napísal:
> I'm no RSS expert, but aren't feeds meant to be read by feed readers
> (bots)? How could the feed work if it's behind bot protection? Is my
> client expected to solve whatever challenge Anubis is posing? Does
> that not defeat the purpose of the bot protection?
curl works here:
curl -i 'https://git.netfilter.org/iptables/atom/?h=master'
Date: Mon, 20 Jul 2026 18:08:39 GMT
Server: Apache
Content-Type: text/xml; charset=utf-8
Expires: Mon, 20 Jul 2026 18:13:26 GMT
Last-Modified: Mon, 20 Jul 2026 18:08:26 GMT
Vary: Accept-Encoding
Transfer-Encoding: chunked
...
Are you sure, that you do not impersonate (fake) real browser? When i
set Firefox's User-Agent header, i hit anubis:
curl -iA "Mozilla/5.0 (X11; Linux x86_64; rv:125.0) Gecko/20100101 Firefox/125.0" ...
HTTP/1.1 200 OK Date: Mon, 20 Jul 2026 18:11:53 GMT
Server: Apache
Cache-Control: no-store
Content-Type: text/html; charset=utf-8
Set-Cookie: techaro.lol-anubis-auth=; Path=/; Expires=Mon, 20 Jul 2026
18:10:53 GMT; Max-Age=0; Secure; SameSite=None Set-Cookie:
techaro.lol-anubis-cookie-verification=019f80ba-316b-7dae-a172-50fdeecbc5ba;
Path=/; Expires=Mon, 20 Jul 2026 18:41:53 GMT; Secure; SameSite=None
Vary: Accept-Encoding Content-Length: 4469
regards
--
Slavko
https://www.slavino.sk
prev parent reply other threads:[~2026-07-20 18:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 17:51 Bot protection on RSS feed for git.netfilter.org netfilter.btvdk
2026-07-20 18:13 ` Slavko [this message]
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=20260720201345.51e926cf@bonifac.skk \
--to=linux@slavino.sk \
--cc=netfilter@vger.kernel.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