<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blazor on Paul Clephan | Intune, ConfigMgr, SCCM &amp; Windows Management Blog</title><link>https://clefsoft.co.uk/tags/blazor/</link><description>Recent content in Blazor on Paul Clephan | Intune, ConfigMgr, SCCM &amp; Windows Management Blog</description><generator>Hugo</generator><language>en-gb</language><lastBuildDate>Fri, 21 Aug 2026 09:15:00 +0100</lastBuildDate><atom:link href="https://clefsoft.co.uk/tags/blazor/index.xml" rel="self" type="application/rss+xml"/><item><title>A Blank Page for Every Anonymous User: How One Global Auth Policy Broke Blazor's Own Framework Endpoints</title><link>https://clefsoft.co.uk/posts/blazor-fallbackpolicy-blank-page/</link><pubDate>Fri, 21 Aug 2026 09:15:00 +0100</pubDate><guid>https://clefsoft.co.uk/posts/blazor-fallbackpolicy-blank-page/</guid><description>I added a public landing page to a Blazor Server app and it rendered as a blank white screen — not just that page, every page, for every anonymous user. No server-side exception. The cause was a global FallbackPolicy quietly gating Blazor&amp;rsquo;s own internal SignalR endpoints.</description></item></channel></rss>