dandri/synapse
1
0 Fork 0
mirror of https://github.com/element-hq/synapse.git synced 2026-10-22 15:22:57 +00:00
Code Issues Packages Projects Releases Wiki Activity

deploy: e9f2ad8603

Browse Source
This commit is contained in:
babolivier committed 2021-06-18 14:56:12 +00:00
1 parent 3c7fd98b40
commit d4892a68c1
4 files changed
+18 -18
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

develop/modules.html
+8 -8
View File
@@ -253,32 +253,32 @@ module API's <code>register_spam_checker_callbacks</code> method. The callback f
to <code>register_spam_checker_callbacks</code> as keyword arguments, with the callback name as the
argument name and the function as its value. This is demonstrated in the example below.</p>
<p>The available spam checker callbacks are:</p>
<pre><code class="language-python">def check_event_for_spam(event: &quot;synapse.events.EventBase&quot;) -&gt; Union[bool, str]
<pre><code class="language-python">async def check_event_for_spam(event: &quot;synapse.events.EventBase&quot;) -&gt; Union[bool, str]
</code></pre>
<p>Called when receiving an event from a client or via federation. The module can return
either a <code>bool</code> to indicate whether the event must be rejected because of spam, or a <code>str</code>
to indicate the event must be rejected because of spam and to give a rejection reason to
forward to clients.</p>
<pre><code class="language-python">def user_may_invite(inviter: str, invitee: str, room_id: str) -&gt; bool
<pre><code class="language-python">async def user_may_invite(inviter: str, invitee: str, room_id: str) -&gt; bool
</code></pre>
<p>Called when processing an invitation. The module must return a <code>bool</code> indicating whether
the inviter can invite the invitee to the given room. Both inviter and invitee are
represented by their Matrix user ID (i.e. <code>@alice:example.com</code>).</p>
<pre><code class="language-python">def user_may_create_room(user: str) -&gt; bool
<pre><code class="language-python">async def user_may_create_room(user: str) -&gt; bool
</code></pre>
<p>Called when processing a room creation request. The module must return a <code>bool</code> indicating
whether the given user (represented by their Matrix user ID) is allowed to create a room.</p>
<pre><code class="language-python">def user_may_create_room_alias(user: str, room_alias: &quot;synapse.types.RoomAlias&quot;) -&gt; bool
<pre><code class="language-python">async def user_may_create_room_alias(user: str, room_alias: &quot;synapse.types.RoomAlias&quot;) -&gt; bool
</code></pre>
<p>Called when trying to associate an alias with an existing room. The module must return a
<code>bool</code> indicating whether the given user (represented by their Matrix user ID) is allowed
to set the given alias.</p>
<pre><code class="language-python">def user_may_publish_room(user: str, room_id: str) -&gt; bool
<pre><code class="language-python">async def user_may_publish_room(user: str, room_id: str) -&gt; bool
</code></pre>
<p>Called when trying to publish a room to the homeserver's public rooms directory. The
module must return a <code>bool</code> indicating whether the given user (represented by their
Matrix user ID) is allowed to publish the given room.</p>
<pre><code class="language-python">def check_username_for_spam(user_profile: Dict[str, str]) -&gt; bool
<pre><code class="language-python">async def check_username_for_spam(user_profile: Dict[str, str]) -&gt; bool
</code></pre>
<p>Called when computing search results in the user directory. The module must return a
<code>bool</code> indicating whether the given user profile can appear in search results. The profile
@@ -290,7 +290,7 @@ is represented as a dictionary with the following keys:</p>
</ul>
<p>The module is given a copy of the original dictionary, so modifying it from within the
module cannot modify a user's profile when included in user directory search results.</p>
<pre><code class="language-python">def check_registration_for_spam(
<pre><code class="language-python">async def check_registration_for_spam(
email_threepid: Optional[dict],
username: Optional[str],
request_info: Collection[Tuple[str, str]],
@@ -310,7 +310,7 @@ second item is an IP address. These user agents and IP addresses are the ones th
used during the registration process.</li>
<li><code>auth_provider_id</code>: The identifier of the SSO authentication provider, if any.</li>
</ul>
<pre><code class="language-python">def check_media_file_for_spam(
<pre><code class="language-python">async def check_media_file_for_spam(
file_wrapper: &quot;synapse.rest.media.v1.media_storage.ReadableFileWrapper&quot;,
file_info: &quot;synapse.rest.media.v1._base.FileInfo&quot;
) -&gt; bool
develop/print.html
+8 -8
View File
@@ -7255,32 +7255,32 @@ module API's <code>register_spam_checker_callbacks</code> method. The callback f
to <code>register_spam_checker_callbacks</code> as keyword arguments, with the callback name as the
argument name and the function as its value. This is demonstrated in the example below.</p>
<p>The available spam checker callbacks are:</p>
<pre><code class="language-python">def check_event_for_spam(event: &quot;synapse.events.EventBase&quot;) -&gt; Union[bool, str]
<pre><code class="language-python">async def check_event_for_spam(event: &quot;synapse.events.EventBase&quot;) -&gt; Union[bool, str]
</code></pre>
<p>Called when receiving an event from a client or via federation. The module can return
either a <code>bool</code> to indicate whether the event must be rejected because of spam, or a <code>str</code>
to indicate the event must be rejected because of spam and to give a rejection reason to
forward to clients.</p>
<pre><code class="language-python">def user_may_invite(inviter: str, invitee: str, room_id: str) -&gt; bool
<pre><code class="language-python">async def user_may_invite(inviter: str, invitee: str, room_id: str) -&gt; bool
</code></pre>
<p>Called when processing an invitation. The module must return a <code>bool</code> indicating whether
the inviter can invite the invitee to the given room. Both inviter and invitee are
represented by their Matrix user ID (i.e. <code>@alice:example.com</code>).</p>
<pre><code class="language-python">def user_may_create_room(user: str) -&gt; bool
<pre><code class="language-python">async def user_may_create_room(user: str) -&gt; bool
</code></pre>
<p>Called when processing a room creation request. The module must return a <code>bool</code> indicating
whether the given user (represented by their Matrix user ID) is allowed to create a room.</p>
<pre><code class="language-python">def user_may_create_room_alias(user: str, room_alias: &quot;synapse.types.RoomAlias&quot;) -&gt; bool
<pre><code class="language-python">async def user_may_create_room_alias(user: str, room_alias: &quot;synapse.types.RoomAlias&quot;) -&gt; bool
</code></pre>
<p>Called when trying to associate an alias with an existing room. The module must return a
<code>bool</code> indicating whether the given user (represented by their Matrix user ID) is allowed
to set the given alias.</p>
<pre><code class="language-python">def user_may_publish_room(user: str, room_id: str) -&gt; bool
<pre><code class="language-python">async def user_may_publish_room(user: str, room_id: str) -&gt; bool
</code></pre>
<p>Called when trying to publish a room to the homeserver's public rooms directory. The
module must return a <code>bool</code> indicating whether the given user (represented by their
Matrix user ID) is allowed to publish the given room.</p>
<pre><code class="language-python">def check_username_for_spam(user_profile: Dict[str, str]) -&gt; bool
<pre><code class="language-python">async def check_username_for_spam(user_profile: Dict[str, str]) -&gt; bool
</code></pre>
<p>Called when computing search results in the user directory. The module must return a
<code>bool</code> indicating whether the given user profile can appear in search results. The profile
@@ -7292,7 +7292,7 @@ is represented as a dictionary with the following keys:</p>
</ul>
<p>The module is given a copy of the original dictionary, so modifying it from within the
module cannot modify a user's profile when included in user directory search results.</p>
<pre><code class="language-python">def check_registration_for_spam(
<pre><code class="language-python">async def check_registration_for_spam(
email_threepid: Optional[dict],
username: Optional[str],
request_info: Collection[Tuple[str, str]],
@@ -7312,7 +7312,7 @@ second item is an IP address. These user agents and IP addresses are the ones th
used during the registration process.</li>
<li><code>auth_provider_id</code>: The identifier of the SSO authentication provider, if any.</li>
</ul>
<pre><code class="language-python">def check_media_file_for_spam(
<pre><code class="language-python">async def check_media_file_for_spam(
file_wrapper: &quot;synapse.rest.media.v1.media_storage.ReadableFileWrapper&quot;,
file_info: &quot;synapse.rest.media.v1._base.FileInfo&quot;
) -&gt; bool
develop/searchindex.js
+1 -1
View File
@@ -1 +1 @@
Object.assign(window.search, {"doc_urls":["welcome_and_overview.html#introduction","setup/installation.html#installation-instructions","setup/installation.html#choosing-your-server-name","setup/installation.html#installing-synapse","setup/installation.html#installing-from-source","setup/installation.html#prebuilt-packages","setup/installation.html#setting-up-synapse","setup/installation.html#using-postgresql","setup/installation.html#tls-certificates","setup/installation.html#client-well-known-uri","setup/installation.html#email","setup/installation.html#registering-a-user","setup/installation.html#setting-up-a-turn-server","setup/installation.html#url-previews","setup/installation.html#troubleshooting-installation","postgres.html#using-postgres","postgres.html#install-postgres-client-libraries","postgres.html#set-up-database","postgres.html#synapse-config","postgres.html#tuning-postgres","postgres.html#porting-from-sqlite","postgres.html#overview","postgres.html#using-the-port-script","postgres.html#troubleshooting","postgres.html#alternative-auth-methods","postgres.html#fixing-incorrect-collate-or-ctype","postgres.html#fixing-inconsistent-sequences-error","reverse_proxy.html#using-a-reverse-proxy-with-synapse","reverse_proxy.html#reverse-proxy-configuration-examples","reverse_proxy.html#nginx","reverse_proxy.html#caddy-1","reverse_proxy.html#caddy-2","reverse_proxy.html#apache","reverse_proxy.html#haproxy","reverse_proxy.html#relayd","reverse_proxy.html#homeserver-configuration","reverse_proxy.html#health-check-endpoint","reverse_proxy.html#synapse-administration-endpoints","turn-howto.html#overview","turn-howto.html#requirements","turn-howto.html#coturn-setup","turn-howto.html#initial-installation","turn-howto.html#configuration","turn-howto.html#synapse-setup","turn-howto.html#troubleshooting","delegate.html#delegation","delegate.html#well-known-delegation","delegate.html#srv-dns-record-delegation","delegate.html#delegation-faq","delegate.html#when-do-i-need-delegation","delegate.html#do-you-still-recommend-against-using-a-reverse-proxy-on-the-federation-port","delegate.html#do-i-still-need-to-give-my-tls-certificates-to-synapse-if-i-am-using-a-reverse-proxy","delegate.html#do-i-need-the-same-certificate-for-the-client-and-federation-port","upgrading/index.html#upgrading-synapse","upgrading/index.html#rolling-back-to-older-versions","upgrading/index.html#replace-130-accordingly","upgrading/index.html#replace-130-and-stretch-accordingly","upgrading/index.html#upgrading-to-v1370","upgrading/index.html#deprecation-of-the-current-spam-checker-interface","upgrading/index.html#upgrading-to-v1340","upgrading/index.html#room_invite_state_types-configuration-setting","upgrading/index.html#upgrading-to-v1330","upgrading/index.html#account-validity-html-templates-can-now-display-a-users-expiration-date","upgrading/index.html#upgrading-to-v1320","upgrading/index.html#regression-causing-connected-prometheus-instances-to-become-overwhelmed","upgrading/index.html#dropping-support-for-old-python-postgres-and-sqlite-versions","upgrading/index.html#removal-of-old-list-accounts-admin-api","upgrading/index.html#application-services-must-use-type-mloginapplication_service-when-registering-users","upgrading/index.html#upgrading-to-v1290","upgrading/index.html#requirement-for-x-forwarded-proto-header","upgrading/index.html#upgrading-to-v1270","upgrading/index.html#changes-to-callback-uri-for-oauth2--openid-connect-and-saml2","upgrading/index.html#changes-to-html-templates","upgrading/index.html#upgrading-to-v1260","upgrading/index.html#rolling-back-to-v1250-after-a-failed-upgrade","upgrading/index.html#upgrading-to-v1250","upgrading/index.html#last-release-supporting-python-35","upgrading/index.html#blacklisting-ip-ranges","upgrading/index.html#upgrading-to-v1240","upgrading/index.html#custom-openid-connect-mapping-provider-breaking-change","upgrading/index.html#removal-historical-synapse-admin-api","upgrading/index.html#upgrading-to-v1230","upgrading/index.html#structured-logging-configuration-breaking-changes","upgrading/index.html#upgrading-to-v1220","upgrading/index.html#thirdpartyeventrules-breaking-changes","upgrading/index.html#upgrading-to-v1210","upgrading/index.html#forwarding-_synapseclient-through-your-reverse-proxy","upgrading/index.html#new-html-templates","upgrading/index.html#updated-single-sign-on-html-templates","upgrading/index.html#upgrading-to-v1180","upgrading/index.html#docker--py3-suffix-will-be-removed-in-future-versions","upgrading/index.html#redis-replication-is-now-recommended-in-lieu-of-tcp-replication","upgrading/index.html#upgrading-to-v1140","upgrading/index.html#upgrading-to-v1130","upgrading/index.html#incorrect-database-migration-in-old-synapse-versions","upgrading/index.html#new-single-sign-on-html-templates","upgrading/index.html#synapse-sso-plugins-method-deprecation","upgrading/index.html#rolling-back-to-v1124-after-a-failed-upgrade","upgrading/index.html#upgrading-to-v1120","upgrading/Line truncated
Object.assign(window.search, {"doc_urls":["welcome_and_overview.html#introduction","setup/installation.html#installation-instructions","setup/installation.html#choosing-your-server-name","setup/installation.html#installing-synapse","setup/installation.html#installing-from-source","setup/installation.html#prebuilt-packages","setup/installation.html#setting-up-synapse","setup/installation.html#using-postgresql","setup/installation.html#tls-certificates","setup/installation.html#client-well-known-uri","setup/installation.html#email","setup/installation.html#registering-a-user","setup/installation.html#setting-up-a-turn-server","setup/installation.html#url-previews","setup/installation.html#troubleshooting-installation","postgres.html#using-postgres","postgres.html#install-postgres-client-libraries","postgres.html#set-up-database","postgres.html#synapse-config","postgres.html#tuning-postgres","postgres.html#porting-from-sqlite","postgres.html#overview","postgres.html#using-the-port-script","postgres.html#troubleshooting","postgres.html#alternative-auth-methods","postgres.html#fixing-incorrect-collate-or-ctype","postgres.html#fixing-inconsistent-sequences-error","reverse_proxy.html#using-a-reverse-proxy-with-synapse","reverse_proxy.html#reverse-proxy-configuration-examples","reverse_proxy.html#nginx","reverse_proxy.html#caddy-1","reverse_proxy.html#caddy-2","reverse_proxy.html#apache","reverse_proxy.html#haproxy","reverse_proxy.html#relayd","reverse_proxy.html#homeserver-configuration","reverse_proxy.html#health-check-endpoint","reverse_proxy.html#synapse-administration-endpoints","turn-howto.html#overview","turn-howto.html#requirements","turn-howto.html#coturn-setup","turn-howto.html#initial-installation","turn-howto.html#configuration","turn-howto.html#synapse-setup","turn-howto.html#troubleshooting","delegate.html#delegation","delegate.html#well-known-delegation","delegate.html#srv-dns-record-delegation","delegate.html#delegation-faq","delegate.html#when-do-i-need-delegation","delegate.html#do-you-still-recommend-against-using-a-reverse-proxy-on-the-federation-port","delegate.html#do-i-still-need-to-give-my-tls-certificates-to-synapse-if-i-am-using-a-reverse-proxy","delegate.html#do-i-need-the-same-certificate-for-the-client-and-federation-port","upgrading/index.html#upgrading-synapse","upgrading/index.html#rolling-back-to-older-versions","upgrading/index.html#replace-130-accordingly","upgrading/index.html#replace-130-and-stretch-accordingly","upgrading/index.html#upgrading-to-v1370","upgrading/index.html#deprecation-of-the-current-spam-checker-interface","upgrading/index.html#upgrading-to-v1340","upgrading/index.html#room_invite_state_types-configuration-setting","upgrading/index.html#upgrading-to-v1330","upgrading/index.html#account-validity-html-templates-can-now-display-a-users-expiration-date","upgrading/index.html#upgrading-to-v1320","upgrading/index.html#regression-causing-connected-prometheus-instances-to-become-overwhelmed","upgrading/index.html#dropping-support-for-old-python-postgres-and-sqlite-versions","upgrading/index.html#removal-of-old-list-accounts-admin-api","upgrading/index.html#application-services-must-use-type-mloginapplication_service-when-registering-users","upgrading/index.html#upgrading-to-v1290","upgrading/index.html#requirement-for-x-forwarded-proto-header","upgrading/index.html#upgrading-to-v1270","upgrading/index.html#changes-to-callback-uri-for-oauth2--openid-connect-and-saml2","upgrading/index.html#changes-to-html-templates","upgrading/index.html#upgrading-to-v1260","upgrading/index.html#rolling-back-to-v1250-after-a-failed-upgrade","upgrading/index.html#upgrading-to-v1250","upgrading/index.html#last-release-supporting-python-35","upgrading/index.html#blacklisting-ip-ranges","upgrading/index.html#upgrading-to-v1240","upgrading/index.html#custom-openid-connect-mapping-provider-breaking-change","upgrading/index.html#removal-historical-synapse-admin-api","upgrading/index.html#upgrading-to-v1230","upgrading/index.html#structured-logging-configuration-breaking-changes","upgrading/index.html#upgrading-to-v1220","upgrading/index.html#thirdpartyeventrules-breaking-changes","upgrading/index.html#upgrading-to-v1210","upgrading/index.html#forwarding-_synapseclient-through-your-reverse-proxy","upgrading/index.html#new-html-templates","upgrading/index.html#updated-single-sign-on-html-templates","upgrading/index.html#upgrading-to-v1180","upgrading/index.html#docker--py3-suffix-will-be-removed-in-future-versions","upgrading/index.html#redis-replication-is-now-recommended-in-lieu-of-tcp-replication","upgrading/index.html#upgrading-to-v1140","upgrading/index.html#upgrading-to-v1130","upgrading/index.html#incorrect-database-migration-in-old-synapse-versions","upgrading/index.html#new-single-sign-on-html-templates","upgrading/index.html#synapse-sso-plugins-method-deprecation","upgrading/index.html#rolling-back-to-v1124-after-a-failed-upgrade","upgrading/index.html#upgrading-to-v1120","upgrading/Line truncated
develop/searchindex.json
+1 -1
View File
@@ -1 +1 @@
{"doc_urls":["welcome_and_overview.html#introduction","setup/installation.html#installation-instructions","setup/installation.html#choosing-your-server-name","setup/installation.html#installing-synapse","setup/installation.html#installing-from-source","setup/installation.html#prebuilt-packages","setup/installation.html#setting-up-synapse","setup/installation.html#using-postgresql","setup/installation.html#tls-certificates","setup/installation.html#client-well-known-uri","setup/installation.html#email","setup/installation.html#registering-a-user","setup/installation.html#setting-up-a-turn-server","setup/installation.html#url-previews","setup/installation.html#troubleshooting-installation","postgres.html#using-postgres","postgres.html#install-postgres-client-libraries","postgres.html#set-up-database","postgres.html#synapse-config","postgres.html#tuning-postgres","postgres.html#porting-from-sqlite","postgres.html#overview","postgres.html#using-the-port-script","postgres.html#troubleshooting","postgres.html#alternative-auth-methods","postgres.html#fixing-incorrect-collate-or-ctype","postgres.html#fixing-inconsistent-sequences-error","reverse_proxy.html#using-a-reverse-proxy-with-synapse","reverse_proxy.html#reverse-proxy-configuration-examples","reverse_proxy.html#nginx","reverse_proxy.html#caddy-1","reverse_proxy.html#caddy-2","reverse_proxy.html#apache","reverse_proxy.html#haproxy","reverse_proxy.html#relayd","reverse_proxy.html#homeserver-configuration","reverse_proxy.html#health-check-endpoint","reverse_proxy.html#synapse-administration-endpoints","turn-howto.html#overview","turn-howto.html#requirements","turn-howto.html#coturn-setup","turn-howto.html#initial-installation","turn-howto.html#configuration","turn-howto.html#synapse-setup","turn-howto.html#troubleshooting","delegate.html#delegation","delegate.html#well-known-delegation","delegate.html#srv-dns-record-delegation","delegate.html#delegation-faq","delegate.html#when-do-i-need-delegation","delegate.html#do-you-still-recommend-against-using-a-reverse-proxy-on-the-federation-port","delegate.html#do-i-still-need-to-give-my-tls-certificates-to-synapse-if-i-am-using-a-reverse-proxy","delegate.html#do-i-need-the-same-certificate-for-the-client-and-federation-port","upgrading/index.html#upgrading-synapse","upgrading/index.html#rolling-back-to-older-versions","upgrading/index.html#replace-130-accordingly","upgrading/index.html#replace-130-and-stretch-accordingly","upgrading/index.html#upgrading-to-v1370","upgrading/index.html#deprecation-of-the-current-spam-checker-interface","upgrading/index.html#upgrading-to-v1340","upgrading/index.html#room_invite_state_types-configuration-setting","upgrading/index.html#upgrading-to-v1330","upgrading/index.html#account-validity-html-templates-can-now-display-a-users-expiration-date","upgrading/index.html#upgrading-to-v1320","upgrading/index.html#regression-causing-connected-prometheus-instances-to-become-overwhelmed","upgrading/index.html#dropping-support-for-old-python-postgres-and-sqlite-versions","upgrading/index.html#removal-of-old-list-accounts-admin-api","upgrading/index.html#application-services-must-use-type-mloginapplication_service-when-registering-users","upgrading/index.html#upgrading-to-v1290","upgrading/index.html#requirement-for-x-forwarded-proto-header","upgrading/index.html#upgrading-to-v1270","upgrading/index.html#changes-to-callback-uri-for-oauth2--openid-connect-and-saml2","upgrading/index.html#changes-to-html-templates","upgrading/index.html#upgrading-to-v1260","upgrading/index.html#rolling-back-to-v1250-after-a-failed-upgrade","upgrading/index.html#upgrading-to-v1250","upgrading/index.html#last-release-supporting-python-35","upgrading/index.html#blacklisting-ip-ranges","upgrading/index.html#upgrading-to-v1240","upgrading/index.html#custom-openid-connect-mapping-provider-breaking-change","upgrading/index.html#removal-historical-synapse-admin-api","upgrading/index.html#upgrading-to-v1230","upgrading/index.html#structured-logging-configuration-breaking-changes","upgrading/index.html#upgrading-to-v1220","upgrading/index.html#thirdpartyeventrules-breaking-changes","upgrading/index.html#upgrading-to-v1210","upgrading/index.html#forwarding-_synapseclient-through-your-reverse-proxy","upgrading/index.html#new-html-templates","upgrading/index.html#updated-single-sign-on-html-templates","upgrading/index.html#upgrading-to-v1180","upgrading/index.html#docker--py3-suffix-will-be-removed-in-future-versions","upgrading/index.html#redis-replication-is-now-recommended-in-lieu-of-tcp-replication","upgrading/index.html#upgrading-to-v1140","upgrading/index.html#upgrading-to-v1130","upgrading/index.html#incorrect-database-migration-in-old-synapse-versions","upgrading/index.html#new-single-sign-on-html-templates","upgrading/index.html#synapse-sso-plugins-method-deprecation","upgrading/index.html#rolling-back-to-v1124-after-a-failed-upgrade","upgrading/index.html#upgrading-to-v1120","upgrading/index.html#upgrading-to-v1100Line truncated
{"doc_urls":["welcome_and_overview.html#introduction","setup/installation.html#installation-instructions","setup/installation.html#choosing-your-server-name","setup/installation.html#installing-synapse","setup/installation.html#installing-from-source","setup/installation.html#prebuilt-packages","setup/installation.html#setting-up-synapse","setup/installation.html#using-postgresql","setup/installation.html#tls-certificates","setup/installation.html#client-well-known-uri","setup/installation.html#email","setup/installation.html#registering-a-user","setup/installation.html#setting-up-a-turn-server","setup/installation.html#url-previews","setup/installation.html#troubleshooting-installation","postgres.html#using-postgres","postgres.html#install-postgres-client-libraries","postgres.html#set-up-database","postgres.html#synapse-config","postgres.html#tuning-postgres","postgres.html#porting-from-sqlite","postgres.html#overview","postgres.html#using-the-port-script","postgres.html#troubleshooting","postgres.html#alternative-auth-methods","postgres.html#fixing-incorrect-collate-or-ctype","postgres.html#fixing-inconsistent-sequences-error","reverse_proxy.html#using-a-reverse-proxy-with-synapse","reverse_proxy.html#reverse-proxy-configuration-examples","reverse_proxy.html#nginx","reverse_proxy.html#caddy-1","reverse_proxy.html#caddy-2","reverse_proxy.html#apache","reverse_proxy.html#haproxy","reverse_proxy.html#relayd","reverse_proxy.html#homeserver-configuration","reverse_proxy.html#health-check-endpoint","reverse_proxy.html#synapse-administration-endpoints","turn-howto.html#overview","turn-howto.html#requirements","turn-howto.html#coturn-setup","turn-howto.html#initial-installation","turn-howto.html#configuration","turn-howto.html#synapse-setup","turn-howto.html#troubleshooting","delegate.html#delegation","delegate.html#well-known-delegation","delegate.html#srv-dns-record-delegation","delegate.html#delegation-faq","delegate.html#when-do-i-need-delegation","delegate.html#do-you-still-recommend-against-using-a-reverse-proxy-on-the-federation-port","delegate.html#do-i-still-need-to-give-my-tls-certificates-to-synapse-if-i-am-using-a-reverse-proxy","delegate.html#do-i-need-the-same-certificate-for-the-client-and-federation-port","upgrading/index.html#upgrading-synapse","upgrading/index.html#rolling-back-to-older-versions","upgrading/index.html#replace-130-accordingly","upgrading/index.html#replace-130-and-stretch-accordingly","upgrading/index.html#upgrading-to-v1370","upgrading/index.html#deprecation-of-the-current-spam-checker-interface","upgrading/index.html#upgrading-to-v1340","upgrading/index.html#room_invite_state_types-configuration-setting","upgrading/index.html#upgrading-to-v1330","upgrading/index.html#account-validity-html-templates-can-now-display-a-users-expiration-date","upgrading/index.html#upgrading-to-v1320","upgrading/index.html#regression-causing-connected-prometheus-instances-to-become-overwhelmed","upgrading/index.html#dropping-support-for-old-python-postgres-and-sqlite-versions","upgrading/index.html#removal-of-old-list-accounts-admin-api","upgrading/index.html#application-services-must-use-type-mloginapplication_service-when-registering-users","upgrading/index.html#upgrading-to-v1290","upgrading/index.html#requirement-for-x-forwarded-proto-header","upgrading/index.html#upgrading-to-v1270","upgrading/index.html#changes-to-callback-uri-for-oauth2--openid-connect-and-saml2","upgrading/index.html#changes-to-html-templates","upgrading/index.html#upgrading-to-v1260","upgrading/index.html#rolling-back-to-v1250-after-a-failed-upgrade","upgrading/index.html#upgrading-to-v1250","upgrading/index.html#last-release-supporting-python-35","upgrading/index.html#blacklisting-ip-ranges","upgrading/index.html#upgrading-to-v1240","upgrading/index.html#custom-openid-connect-mapping-provider-breaking-change","upgrading/index.html#removal-historical-synapse-admin-api","upgrading/index.html#upgrading-to-v1230","upgrading/index.html#structured-logging-configuration-breaking-changes","upgrading/index.html#upgrading-to-v1220","upgrading/index.html#thirdpartyeventrules-breaking-changes","upgrading/index.html#upgrading-to-v1210","upgrading/index.html#forwarding-_synapseclient-through-your-reverse-proxy","upgrading/index.html#new-html-templates","upgrading/index.html#updated-single-sign-on-html-templates","upgrading/index.html#upgrading-to-v1180","upgrading/index.html#docker--py3-suffix-will-be-removed-in-future-versions","upgrading/index.html#redis-replication-is-now-recommended-in-lieu-of-tcp-replication","upgrading/index.html#upgrading-to-v1140","upgrading/index.html#upgrading-to-v1130","upgrading/index.html#incorrect-database-migration-in-old-synapse-versions","upgrading/index.html#new-single-sign-on-html-templates","upgrading/index.html#synapse-sso-plugins-method-deprecation","upgrading/index.html#rolling-back-to-v1124-after-a-failed-upgrade","upgrading/index.html#upgrading-to-v1120","upgrading/index.html#upgrading-to-v1100Line truncated