JoyProxy endpoints support common consumer and enterprise patterns: HTTP proxy, HTTPS proxy (HTTP CONNECT tunneling), and SOCKS5. The “best” choice is whichever your runtime supports cleanly—not whichever name sounds more secure.
HTTP / HTTPS proxy
Most HTTP client libraries (Python requests, Node axios, Java OkHttp) accept an http://user:pass@host:port proxy URL. HTTPS targets still work: the client issues a CONNECT tunnel through the proxy. Use this path when your stack already documents HTTP proxy support.
SOCKS5
SOCKS5 operates at a lower layer—useful for non-HTTP traffic, some mobile tooling, or frameworks that expose a single SOCKS port. JoyProxy’s open-source Android client and Linux gateway also speak SOCKS5 for downstream apps.
Quick compatibility table
| Scenario | Typical protocol |
|---|---|
| Python scrapers (requests, httpx) | HTTP proxy URL |
| Playwright / Puppeteer | HTTP or SOCKS5 per browser docs |
| Mobile per-app routing | SOCKS5 via Android client |
| Legacy enterprise apps | Often HTTP; sometimes SOCKS5 only |
TLS and certificate pitfalls
Traffic between your app and the proxy may be unencrypted HTTP even when the target URL is HTTPS—the tunnel encrypts from proxy to site. Do not disable TLS verification on the final connection unless you understand the MITM implications of your tooling.
If a connection fails only on HTTPS sites, verify CONNECT support and authentication headers before blaming IP reputation.