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

Is your feature request related to a problem? Please describe.

This is the logic currently implemented in the main branch:

If headers criteria are configured, a request is filtered in if it matches both headers and urls. If headers criteria are NOT configured, the probability options are used.

Describe the solution you'd like

I want to take the URL check when no header is

Is your feature request related to a problem? Please describe.

Not related to a problem

Describe the solution you'd like

We opened #808 to discuss how we might use GitHub actions. At the time, this repo didn't have actions enabled. Now that it does, we should try them out for some of the things in that thread.

_Edit from @arschles - we have focused this issue to just the twitte

Under multiport mode, plugins may need to know on which port was the request received/accepted. This information is currently not surfaced to plugins. For background also see abhinavsingh/proxy.py#535 (comment) thread

• 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');