MatrixSynapse

Commit Graph

Author	SHA1	Message	Date
Marcus	e385c8b473	Don't apply the IP range blacklist to proxy connections (#9084 ) It is expected that the proxy would be on a private IP address so the configured proxy should be connected to regardless of the IP range blacklist.	2021-01-12 12:20:30 -05:00
Richard van der Hoff	1cb84c6486	Support for routing outbound HTTP requests via a proxy (#6239 ) The `http_proxy` and `HTTPS_PROXY` env vars can be set to a `host[:port]` value which should point to a proxy. The address of the proxy should be excluded from IP blacklists such as the `url_preview_ip_range_blacklist`. The proxy will then be used for * push * url previews * phone-home stats * recaptcha validation * CAS auth validation It will not be used for: * Application Services * Identity servers * Outbound federation * In worker configurations, connections from workers to masters Fixes #4198.	2019-11-01 14:07:44 +00:00

Author

SHA1

Message

Date

Marcus

e385c8b473

Don't apply the IP range blacklist to proxy connections (#9084 )

It is expected that the proxy would be on a private IP address so the
configured proxy should be connected to regardless of the IP range
blacklist.

2021-01-12 12:20:30 -05:00

Richard van der Hoff

1cb84c6486

Support for routing outbound HTTP requests via a proxy (#6239 )

The `http_proxy` and `HTTPS_PROXY` env vars can be set to a `host[:port]` value which should point to a proxy.

The address of the proxy should be excluded from IP blacklists such as the `url_preview_ip_range_blacklist`.

The proxy will then be used for
 * push
 * url previews
 * phone-home stats
 * recaptcha validation
 * CAS auth validation

It will *not* be used for:
 * Application Services
 * Identity servers
 * Outbound federation
 * In worker configurations, connections from workers to masters

Fixes #4198.

2019-11-01 14:07:44 +00:00

2 Commits (15090de85075c9d7d54479b4bfd79057de64059b)