Skip to main content
URL forwarding mode is the recommended approach for HTTPS APIs. Instead of tunnelling, you send requests to Proxy Hopper with a X-Proxy-Hopper-Target header specifying the target. Proxy Hopper reconstructs the full URL and makes the HTTPS request itself — owning the connection end-to-end. Because Proxy Hopper owns the full request, it can retry on 429 or 5xx responses, rotating to a different IP each time, without the client knowing.

​
Usage

Set X-Proxy-Hopper-Target to the target scheme and host, then send requests to Proxy Hopper as if it were the target server: 
curl -H "X-Proxy-Hopper-Target: https://api.example.com" \
     http://localhost:8080/v1/endpoint?q=search
The header value may include a base path (https://api.example.com/v2) which is prepended to the request path.

​
Characteristics

PropertyDetail
ProtocolHTTP with custom header
HTTPS supportYes
Retry supportYes — full retry and IP rotation on failure
Client changes requiredChange base URL + add header

​
When to use it

URL forwarding is the best choice when:
  • You’re hitting HTTPS APIs and need retry support
  • You’re scraping or polling at scale and want maximum resilience
  • You can modify your HTTP client’s base URL (most API clients support this)