From 1d9d9205d60b66092dab50a11bc716d150b0f448 Mon Sep 17 00:00:00 2001
From: DMRobertson <DMRobertson@users.noreply.github.com>
Date: Wed, 16 Nov 2022 22:17:06 +0000
Subject: deploy: c15e9a0edb696990365ac5a4e5be847b5ae23921

---
 develop/workers.html | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

(limited to 'develop/workers.html')

diff --git a/develop/workers.html b/develop/workers.html
index c66bc2f86f..95ec9edf4c 100644
--- a/develop/workers.html
+++ b/develop/workers.html
@@ -252,8 +252,8 @@ The currently available worker applications are listed <a href="#available-worke
 <a href="usage/configuration/config_documentation.html#worker_replication_http_port"><code>worker_replication_http_port</code></a>).</li>
 <li>If handling HTTP requests, a <a href="usage/configuration/config_documentation.html#worker_listeners"><code>worker_listeners</code></a> option
 with an <code>http</code> listener.</li>
-<li>If handling the <code>^/_matrix/client/v3/keys/upload</code> endpoint, the HTTP URI for
-the main process (<code>worker_main_http_uri</code>).</li>
+<li><strong>Synapse 1.71 and older:</strong> if handling the <code>^/_matrix/client/v3/keys/upload</code> endpoint, the HTTP URI for
+the main process (<code>worker_main_http_uri</code>). This config option is no longer required and is ignored when running Synapse 1.72 and newer.</li>
 </ul>
 <p>For example:</p>
 <pre><code class="language-yaml">worker_app: synapse.app.generic_worker
@@ -342,7 +342,6 @@ information.</p>
 ^/_matrix/client/(api/v1|r0|v3|unstable)/search$
 
 # Encryption requests
-# Note that ^/_matrix/client/(r0|v3|unstable)/keys/upload/ requires `worker_main_http_uri`
 ^/_matrix/client/(r0|v3|unstable)/keys/query$
 ^/_matrix/client/(r0|v3|unstable)/keys/changes$
 ^/_matrix/client/(r0|v3|unstable)/keys/claim$
@@ -496,7 +495,7 @@ responsible for</p>
 <li>persisting them to the DB, and finally</li>
 <li>updating the events stream.</li>
 </ul>
-<p>Because load is sharded in this way, you <em>must</em> restart all worker instances when 
+<p>Because load is sharded in this way, you <em>must</em> restart all worker instances when
 adding or removing event persisters.</p>
 <p>An <code>event_persister</code> should not be mistaken for an <code>event_creator</code>.
 An <code>event_creator</code> listens for requests from clients to create new events and does
-- 
cgit 1.4.1