<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Same-Origin Policy on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/same-origin-policy/</link><description>Recent content in Same-Origin Policy on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 07 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/same-origin-policy/index.xml" rel="self" type="application/rss+xml"/><item><title>How CORS Works: Deep Dive into Internals</title><link>https://ai-blog.noorshomelab.dev/how-it-works/how-cors-works/</link><pubDate>Wed, 07 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/how-it-works/how-cors-works/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Cross-Origin Resource Sharing (CORS) is a crucial security mechanism implemented in web browsers that governs how web pages in one &amp;ldquo;origin&amp;rdquo; can request resources from another &amp;ldquo;origin.&amp;rdquo; In simpler terms, it&amp;rsquo;s a gatekeeper that decides whether your browser can load data from a different domain, protocol, or port than the one the current web page originated from. Without CORS, the rigid Same-Origin Policy would severely limit the capabilities of modern web applications, preventing them from interacting with APIs hosted on separate servers, integrating third-party services, or distributing content across various subdomains.&lt;/p&gt;</description></item><item><title>How Web Storage Mechanisms Work: Deep Dive into Internals</title><link>https://ai-blog.noorshomelab.dev/how-it-works/how-web-storage-mechanisms-work-deep-dive/</link><pubDate>Wed, 07 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/how-it-works/how-web-storage-mechanisms-work-deep-dive/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;The modern web is built upon a fundamental paradox: HTTP, the protocol driving it, is inherently stateless. Each request a browser makes to a server is treated as an independent event, with no inherent memory of past interactions. Yet, user experience demands continuity – remembering login states, personalized settings, shopping cart contents, or even data for offline access. This challenge led to the development of various client-side data storage mechanisms, each designed to persist information across requests, sessions, or even browser closures.&lt;/p&gt;</description></item></channel></rss>