The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.
--- Begin Message ---
A friend recently pointed out a very useful tool that could solve our
issues: https://gitlab.com/grouperenault/git_cdn
This tool allows us to set up a cache near our CI/Buildbot workers,
eliminating issues related to scraping. We could potentially run two
separate instances: one for GitHub and another for git.openwrt.org.
On 12/6/24 11:52 AM, Bjørn Mork wrote:
Petr Štetiar <yn...@true.cz> writes:
Hannu Nyman <hannu.ny...@iki.fi> [2024-12-04 17:23:39]:
Or alternatively, set feeds.conf.default to point to the new
git.cdn.openwrt.org?
CDNs are not able to handle/cache this Git HTTP smart protocol yet, so it
wouldn't help with Git fetching operations, this would be basically still
passthru mode. CDN is going to lower the load from gitweb based scrapers which
are not using proper Bot user agent in HTTP headers (those are already rate
limited).
How about something like https://github.com/google/goblet ? Maybe
even with a CDN in front of it.
Bjørn
_______________________________________________
openwrt-adm mailing list
openwrt-...@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-adm
--- End Message ---
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
