proxy-server

Right now the encryptionMethod is fixed to chacha20-ietf-poly1305:

https://github.com/Jigsaw-Code/outline-server/blob/037430d732d7e7bcfd2fc0f33cdbee39ce66fe79/src/shadowbox/server/server_access_key.ts#L87

Here are the recommended methods in shadowsocks:

• aes-128-gcm, aes-256-gcm
• chacha20-ietf-poly1305

Modern hardwares (CPUs) have crypto instructions that support AES encryption

Describe the bug
CodeQL show that we are logging paths directly. We should instead escape and then log them.

To Reproduce
Results are shown here: https://github.com/gomods/athens/pull/1748/checks?check_run_id=4567576462

Expected behavior

We can simply log escaped paths provided by net/url: https://pkg.go.dev/net/url#URL.EscapedPath

Additional context
Add an

Integration tests must exist under both normal and TLS interception mode.

See https://github.com/abhinavsingh/proxy.py/tree/develop/tests/integration for existing integration tests.

• Introduce and implement circuit breaker pattern for weaver

It would be nice to have a validation every time ergo runs in order to avoid badly formatted files and undefined errors.

Simply modified your code on handler_forward.js

// custom `http.Agent` support, set `server.httpAgent`
if (!!this.server.httpAgent) reqOpts.agent = this.server.httpAgent;

And in server.js in constructor add
this.httpAgent = options.httpAgent;

Then, if we want to create server with socks proxy for example, do this:

const { SocksProxyAgent } = require('socks-proxy-agent');