<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Cookies on BareProxy.com</title>
    <link>https://bareproxy.com/tags/cookies/</link>
    <description>Recent content in Cookies on BareProxy.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 08 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://bareproxy.com/tags/cookies/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>BareProxy Cookie Consent Plugin: A Consent Banner and Cookie Blocking at the Proxy</title>
      <link>https://bareproxy.com/bareproxy-cookie-consent-plugin-a-consent-banner-and-cookie-blocking-at-the-proxy/</link>
      <pubDate>Thu, 08 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://bareproxy.com/bareproxy-cookie-consent-plugin-a-consent-banner-and-cookie-blocking-at-the-proxy/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Status: planned, number 13 of 21 in BareProxy&amp;rsquo;s build order.&lt;/strong&gt; The plugins are built easiest first, and this one is about two days of coding: a banner in HTML pages and cookies held back by category. It comes after the Markdown serving plugin. This post describes what it will do, and it will be updated as it is built.&lt;/p&gt;&#xA;&lt;p&gt;Under the EU&amp;rsquo;s ePrivacy rules and the GDPR, a site needs consent before it sets cookies that aren&amp;rsquo;t strictly necessary: analytics, advertising, embedded third-party content. Most sites handle it with a consent platform loaded as a script, which adds weight to every page and only works as well as the site&amp;rsquo;s code that is supposed to wait for it.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
