-
-
Notifications
You must be signed in to change notification settings - Fork 6
proxy support: add support for proxy creds and no_proxy config #70
Comments
@MatMaul could you post the contents of the patch (without the credentials of course) so we could see what exactly you're changing? Otherwise in terms of additional parsing, what we currently parse is done here: synapse-dinsic/synapse/http/proxyagent.py Lines 172 to 207 in 63e8ab5
This would involve adding a conditional to using the proxy for (for right now) requests to the Identity Service. There's a limited number of places that Synapse attempts to contact an identity server. It usually makes use of |
related: matrix-org/synapse#9000 |
The |
|
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Proxy-Authorization#directives describes the method of transforming username/password information into a base64 encoded string. It's just |
|
Opened a PR on mainline to address proxy credentials: matrix-org/synapse#9657 |
Addresses matrix-org/synapse-dinsic#70 This PR causes `ProxyAgent` to attempt to extract credentials from an `HTTPS_PROXY` env var. If credentials are found, a `Proxy-Authorization` header ([details](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Proxy-Authorization)) is sent to the proxy server to authenticate against it. The headers are *not* passed to the remote server. Also added some type hints.
Addresses #70 This PR causes `ProxyAgent` to attempt to extract credentials from an `HTTPS_PROXY` env var. If credentials are found, a `Proxy-Authorization` header ([details](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Proxy-Authorization)) is sent to the proxy server to authenticate against it. The headers are *not* passed to the remote server. Also added some type hints.
…ne (#95) * Allow providing credentials to HTTPS_PROXY (#9657) Addresses #70 This PR causes `ProxyAgent` to attempt to extract credentials from an `HTTPS_PROXY` env var. If credentials are found, a `Proxy-Authorization` header ([details](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Proxy-Authorization)) is sent to the proxy server to authenticate against it. The headers are *not* passed to the remote server. Also added some type hints. * lint
Currently the credentials to use the proxy are injected through a local patch in the deploy machine.
Would be nice to parse that from the https_proxy string instead.
Also we would need some
no_proxy
support, since we want to be able to both reach internal Tchap Sygnal (no proxy) and matrix.org Sygnal (proxy needed).The text was updated successfully, but these errors were encountered: