Lab testing
Proxy
Multi-protocol edge proxy for HTTP, HTTPS, and SOCKS5
Rust proxy service with per-mode listener controls, optional HTTPS auth, domain blacklist filtering, response caching, and config reload.
What ships on day one
- Run HTTP, HTTPS, and SOCKS5 listeners concurrently with independent ports
- Optional HTTPS basic/bearer authentication and TLS cert/key configuration
- Cache responses in memory (Moka) or Redis with blacklist-aware routing
Deployment choices
Deploy as a single proxy service and choose the traffic modes, auth, and caching setup that match your environment.
- Self Hosted
Engineering blueprint
Practical control without extra complexity.
Traffic modes
- Run HTTP, HTTPS, and SOCKS5 from one service
- Enable only the modes you need and set ports per mode
- Keep default behavior simple while expanding mode-by-mode
Access controls
- HTTPS can be protected with basic auth or bearer tokens
- TLS certificates are required before HTTPS can be enabled
- Blocked domain lists can be applied from config
Performance and operations
- Response caching supports in-memory mode or Redis
- Request logs make it easier to track forwarding and cache hits
- Config changes can be reloaded without a full restart
Request logs
Tracks forwarded requests, status codes, and cache-hit behavior
Mode visibility
Shows which listeners are active so changes are easy to verify
Config reload status
Reports when config updates succeed or are rejected
Operational readiness
Cutovers that keep sessions flowing.
- Works for phased migration from existing HTTP proxies
- Supports stricter HTTPS-only paths where needed
- Ships as Linux binaries and container images for standard rollout patterns
Next step
Want a migration plan for your proxy stack?
Email labs@titaniumguard.in for migration support and deployment planning.