<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Network on vanityURLs</title><link>https://vanityurls.link/en/tags/network/</link><description>Recent content in Network on vanityURLs</description><generator>Hugo</generator><language>en-CA</language><lastBuildDate>Mon, 15 Jun 2026 22:51:56 -0400</lastBuildDate><atom:link href="https://vanityurls.link/en/tags/network/index.xml" rel="self" type="application/rss+xml"/><item><title>Keep scanner traffic out of the Worker</title><link>https://vanityurls.link/en/blog/layering-cloudflare-protection-around-a-short-link-domain/</link><pubDate>Fri, 22 May 2026 00:00:00 +0000</pubDate><guid>https://vanityurls.link/en/blog/layering-cloudflare-protection-around-a-short-link-domain/</guid><description>&lt;p&gt;A short-link redirector looks simple: receive a slug, look up a destination, redirect.&lt;/p&gt;
&lt;p&gt;The internet supplies the rest. PHP probes. WordPress paths. Odd methods. Bot traffic. Crawlers. Repeated misses for slugs nobody created.&lt;/p&gt;
&lt;p&gt;The Worker should not be the first place that noise gets expensive. vanityURLs keeps the Worker small and deterministic, then uses Cloudflare edge controls for traffic that should never spend Worker CPU or analytics quota.&lt;/p&gt;
&lt;h2 id="block-before-runtime"&gt;Block Before Runtime&lt;/h2&gt;
&lt;p&gt;The Worker still validates destinations and runtime policy. That is the last line of defense, not the first.&lt;/p&gt;</description></item></channel></rss>