The v4v6 option only has a usage one ipv6 socket: https://serverfault.com/q/747895



Signed-off-by: Flakebi <flakebi@t-online.de>

In worker mode, on the federation sender, when we receive an edu for sending
over the replication socket, it is parsed into an Edu object. There is no point
extracting the contents of it so that we can then immediately build another Edu.

We were logging this when it was not true.

* make 'event_id' a required parameter in federated state requests

As per the spec: https://matrix.org/docs/spec/server_server/r0.1.1.html#id40



Signed-off-by: Joseph Weston <joseph@weston.cloud>

* add changelog entry for bugfix

Signed-off-by: Joseph Weston <joseph@weston.cloud>

* Update server.py

* Fix parsing of Content-Disposition headers

TIL: filenames in content-dispostion headers can contain semicolons, and aren't
%-encoded.

* fix python2 incompatibility

* Fix docstrings

Move /account/3pid to client_reader

When presence is disabled don't send over replication

Co-Authored-By: erikjohnston <erikj@jki.re>

Move server key queries to federation reader

Fix tightloop over connecting to replication server

* Fix check-newsfragment script

I previously broke this so that it always succeeded...

* more fixes

* fix newsfiles

So that it actually works. See https://httpd.apache.org/docs/2.4/mod/mod_proxy.html#proxypass



Signed-off-by: Paul Tötterman <paul.totterman@iki.fi>

Otherwise if you have many workers they can easily take out master with
their connection attempts

If the client failed to process incoming commands during the initial set
up of the replication connection it would immediately disconnect and
reconnect, resulting in a tightloop.

This can happen, for example, when subscribing to a stream that has a
row that is too long in the backlog.

The fix here is to not consider the connection successfully set up until
the client has succesfully subscribed and caught up with the streams.
This ensures that the retry logic timers aren't reset until then,
meaning that if an error does happen during start up the client will
continue backing off before retrying again.

 Prevent showing non-fed rooms in fed /publicRooms v2

Revert "Prevent showing non-fed rooms in fed /publicRooms"