<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Django on Start AI Tools - Presented by Intent Solutions</title><link>https://startaitools.com/tags/django/</link><description>Recent content in Django on Start AI Tools - Presented by Intent Solutions</description><generator>Hugo</generator><language>en-US</language><copyright>Intent Solutions. All rights reserved.</copyright><lastBuildDate>Thu, 29 Oct 2026 08:00:00 -0600</lastBuildDate><atom:link href="https://startaitools.com/tags/django/index.xml" rel="self" type="application/rss+xml"/><item><title>Referrer-Policy same-origin: Django CSRF 403 Origin null</title><link>https://startaitools.com/posts/referrer-policy-no-referrer-origin-null-csrf-403/</link><pubDate>Thu, 29 Oct 2026 08:00:00 -0600</pubDate><guid>https://startaitools.com/posts/referrer-policy-no-referrer-origin-null-csrf-403/</guid><description>&lt;p&gt;A strict Referrer-Policy header can make every real visitor&amp;rsquo;s form post fail with a 403 while your test suite stays green. This post covers why that happens, which header value avoids it, and the access-log leak that the safe value opens up.&lt;/p&gt;
&lt;p&gt;The app is a Django access-request site. It mails each applicant a one-time link, and the link opens a token page where the applicant confirms the request, finishes setup or withdraws. The token sits in the page URL, so the Referer header matters here.&lt;/p&gt;</description></item></channel></rss>