Synapse 1.50.0 returns 404 Unrecognized request for all client requests if a `webclient` resource is enabled

[anoadragon453]

Update: A fix has been released in Synapse 1.50.1. Please update to that instead of 1.50.0.

TL;DR if you have the client and webclient resources enabled on a port in your listeners config section, attempts to access client resources may fail with a 404, breaking client functionality. Workaround is to either:

• Re-order your resources config option such that webclient appears before client. Example:

  resources:
    - names: [webclient, client, ...]
    ...

  though note that if you rely on the webclient resource, this workaround will render it inaccessible. Thus it is functionally equivalent to the next workaround:

• Remove webclient from your list of resources, or

• downgrade to Synapse 1.49.2.

First noticed in #11762.

This first appears to be related to changes made in #11602

[anoadragon453]

A fix for this issue was implemented in #11764 and has been released in Synapse v1.50.1.