From ecf8cd33e114d592c64cb426ae35a39c1409e914 Mon Sep 17 00:00:00 2001
From: Soren Stoutner <soren@stoutner.com>
Date: Thu, 23 Mar 2023 14:22:23 -0700
Subject: [PATCH] Add a Handbook section about HTTP Pings. 
 https://redmine.stoutner.com/issues/976

---
 doc/index.docbook | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/doc/index.docbook b/doc/index.docbook
index c519d0e..0d0e6f8 100644
--- a/doc/index.docbook
+++ b/doc/index.docbook
@@ -302,6 +302,25 @@
       </para>
     </sect1>
 
+    <!-- HTTP Pings. -->
+    <sect1 id="http-pings">
+      <title>HTTP Pings</title>
+
+      <para>
+        HTTP hyperlinks can have an extra <ulink url="https://developer.mozilla.org/en-US/docs/Web/HTML/Element/a#ping">ping attribute</ulink> that sends a POST request to a different URL.
+        These HTTP pings are commonly used for tracking.
+        <ulink url="https://www.theregister.com/2019/04/06/apple_safari_changes/">Most browsers</ulink> send HTTP pings without informing the user
+        <ulink url="https://lists.w3.org/Archives/Public/public-html/2018May/0027.html">in any way</ulink>
+        (despite what The Register article says, current versions of FireFox also happily send HTTP pings).
+      </para>
+
+      <para>
+        Privacy Browser blocks all HTTP pings and presents a dialog informing the user every time the current tab attempts to send one.
+        Hopefully, as more people become aware of what HTTP pings are, web sites will become more embarrassed about using them.
+        This is a classic example of how those who wrote the HTTP specs do not have the best interests of internet users at heart. I would like the day to come where they are removed from the specs.
+      </para>
+    </sect1>
+
     <!-- Spell Checking. -->
     <sect1 id="spell-checking">
       <title>Spell Checking</title>
-- 
2.43.0