Proxy Edge

INTERNAL SERVICE

Session-based HTTP CONNECT tunnel gateway. TLS is handled by the platform. Each session pins to one SOCKS5 proxy droplet for the duration of the job.

Usage: call GET /proxy/session to get a session ID, then set X-Proxy-Session: <id> on each CONNECT request. Browsers that cannot set CONNECT headers may instead answer the 407 challenge with Proxy-Authorization: Basic — username is the session ID, password is the service key.

GET

/health

Pool size, session count, per-proxy health with timestamps

GET

/proxy/session

Allocate a session — returns { sessionId, ip }

DELETE

/proxy/session/:id

Release a session when the job completes

CONNECT

host:port

Tunnel via X-Proxy-Session header or Basic Proxy-Authorization — routes through pinned droplet SOCKS5