proxy-chain
proxy-chain copied to clipboard
apify
Node.js implementation of a proxy server (think Squid) with support for SSL, authentication and upstream proxy chaining.
Problem -- PR #619 introduced useful HTTP agent pooling functionality, but the current test suite lacks adequate coverage for HTTPS upstreams. - We currently have limited tooling for comprehensive HTTPS...
These are few tests that proofs missing tls overhead when https upstream is used. There should be 2 test cases which will be failing. Checklist: - [ ] Create a...
When an error happens in the chaining it is only logged, but not emitted. I created the event `tunnelError` that emit the error related to the tunnel.
When using an HTTPS upstream proxy, connection statistics (trgRxBytes/trgTxBytes) only count application-layer bytes and miss TLS overhead. This affects both handlers: - forward.ts (HTTP requests via HTTPS upstream) - chain.ts...
This pull request introduces a new `requestFinished` event to enable per-request tracking, complementing the existing socket-level tracking provided by the `connectionClosed` event. Implements #589 ## Key Changes: - **New `requestFinished`...
Currently, the library emits a `connectionClosed` event, which is helpful for tracking the overall bandwidth usage of a socket connection. However, in many real-world scenarios involving persistent connections (e.g., HTTP...
Hi, please export the constants from `badGatewayStatusCodes`. This will allow avoiding duplication across projects.
Currently, the tests are still in plain JS. We should rewrite them to TS. We should also remove the ignore for the `test` folder in the eslint config. Lastly, we...
