Slavi Pantaleev f0698ee641 Do not overwrite X-Forwarded-For when reverse-proxying to Synapse ... We have a flow like this: 1. matrix.DOMAIN vhost (matrix-domain.conf) 2. matrix-synapse vhost (matrix-synapse.conf); or matrix-corporal container, if enabled 3. (optional) matrix-synapse vhost (matrix-synapse.conf), if matrix-corporal enabled 4. matrix-synapse container We are setting `X-Forwarded-For` correctly in step #1, but were overwriting it in step #2 with something inaccurate. Not doing anything in step #2 is better than doing the wrong thing. It's probably best if we append another reverse-proxy address there though, although what we're doing now (with this patch) seems to yield the correct result (when matrix-corporal is not enabled). When matrix-corporal is enabled, we still seem to do the wrong thing for some reason. It's something to be fixed later on.		2021-03-08 17:24:09 +02:00
..
matrix-base-domain.conf.j2	Get matrix-corporal to play nicely with a Synapse worker setup	2021-01-25 09:46:41 +02:00
matrix-client-element.conf.j2	Remove useless quotes around ssl_ciphers value	2021-01-08 21:22:44 +02:00
matrix-dimension.conf.j2	Remove useless quotes around ssl_ciphers value	2021-01-08 21:22:44 +02:00
matrix-domain.conf.j2	Make nginx proxy config (when disabled) obey matrix_federation_public_port	2021-02-24 08:19:20 +02:00
matrix-grafana.conf.j2	Grafana nginx proxy config	2021-02-10 22:54:14 +01:00
matrix-jitsi.conf.j2	Fix point overlap between matrix-domain and Jitsi	2021-03-01 20:27:45 +02:00
matrix-riot-web.conf.j2	Remove useless quotes around ssl_ciphers value	2021-01-08 21:22:44 +02:00
matrix-synapse.conf.j2	Do not overwrite X-Forwarded-For when reverse-proxying to Synapse	2021-03-08 17:24:09 +02:00
nginx-http.conf.j2	Riot is now Element	2020-07-17 11:31:20 +03:00