<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Nginx on nsys.dev Tech Blog</title>
		<link>https://blog.nsys.dev/en/tags/nginx/</link>
		<description>Recent content in Nginx on nsys.dev Tech Blog</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Fri, 12 Jun 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://blog.nsys.dev/en/tags/nginx/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Stopping distributed scraping with country-level CIDR, on stock nginx</title>
				<link>https://blog.nsys.dev/en/posts/nginx-geo-country-block/</link>
				<pubDate>Fri, 12 Jun 2026 00:00:00 +0000</pubDate>
				<guid>https://blog.nsys.dev/en/posts/nginx-geo-country-block/</guid>
				<description>&lt;p&gt;On a certain website, I noticed traffic from a particular country&amp;rsquo;s IPs had grown noticeably. Looking closer, it wasn&amp;rsquo;t the usual &amp;ldquo;one server hammering you&amp;rdquo; type — it was scraping &lt;strong&gt;spread across a great many IPs, each at a modest pace&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;p&gt;This is a record of how I read its nature, chose how to block it by &amp;ldquo;blast radius&amp;rdquo; (the range of damage if something breaks), and rolled it out without stopping the running servers. I hope it offers a clue to anyone troubled by similar distributed access.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
