Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

frontend_proxy worker claims it forwards requests to the main process, but it doesn't #3717

Closed
turt2live opened this issue Aug 18, 2018 · 2 comments · Fixed by #13645
Closed
Assignees
Labels
A-Docs things relating to the documentation

Comments

@turt2live
Copy link
Member

Having ensured I set up the worker_main_http_uri to point to the main process, making a request to something like /_matrix/client/versions results in a 400 unrecognized request. There's no evidence that it actually tries to contact the main process (no additional logging in the worker or main process)

@erikjohnston
Copy link
Member

The frontend proxy only proxies certain paths: https://github.com/matrix-org/synapse/blob/master/docs/workers.rst#synapseappfrontend_proxy, which does not include /_matrix/client/versions

@erikjohnston
Copy link
Member

erikjohnston commented Aug 28, 2018

Oh, the docs are wrong:

It will proxy any requests it cannot handle to the main synapse instance. It must therefore be configured with the location of the main instance, via the worker_main_http_uri setting in the frontend_proxy worker configuration file.

@neilisfragile neilisfragile added the A-Docs things relating to the documentation label Aug 28, 2018
richvdh added a commit that referenced this issue Aug 26, 2022
This has been the same as a generic_worker since #6964, so let's get rid of it.

Fixes #3717
richvdh added a commit that referenced this issue Aug 30, 2022
This has been the same as a generic_worker since #6964, so let's get rid of it.

Fixes #3717
@richvdh richvdh self-assigned this Sep 1, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A-Docs things relating to the documentation
Projects
None yet
4 participants