HTTP proxies
HTTP and HTTPS proxies that work with every tool
Use the protocol every scraper, browser and HTTP library already supports. Point any client at one gateway, put targeting in the username and reach HTTP and HTTPS sites through residential, mobile, ISP or datacenter IPs.
# HTTPS target: curl opens a CONNECT tunnel through the gateway (-v shows it)
curl -sv -x http://gw.proxonym.com:8000 -U "USERNAME-country-us:PASSWORD" \
https://api.ipify.org 2>&1 | grep -E "CONNECT|HTTP/"
# Plain HTTP target: the proxy forwards the request itself
curl -x http://gw.proxonym.com:8000 -U "USERNAME-country-gb:PASSWORD" http://api.ipify.org
# Most tools also read the standard proxy environment variables
export http_proxy="http://USERNAME-country-us:[email protected]:8000"
export https_proxy="$http_proxy"
curl https://api.ipify.orgThe basics
What are HTTP proxies?
An HTTP proxy sits between your client and the website. For a plain http:// URL, your client sends the full request to the proxy, which forwards it to the target and returns the response. For an https:// URL, the client first sends a CONNECT request, the proxy opens a tunnel to the target, and TLS is negotiated straight through it, so the content stays encrypted between your client and the site.
Because almost every tool understands this protocol, an HTTP proxy is the simplest way to change your exit IP: set one proxy URL in cURL, Python requests, Scrapy, Puppeteer, Playwright or Selenium and every request follows it. The same URL serves both HTTP and HTTPS targets.
On Proxonym, the residential and mobile gateway listens on gw.proxonym.com:8000, shared datacenter IPs use port 3129, and ISP and dedicated proxies use the port shown in your list. Our integration guides show the exact setup for each tool.
| Feature | HTTP target | HTTPS target |
|---|---|---|
| How the proxy handles it | Forwards the full request | Opens a CONNECT tunnel |
| Encryption | None, readable in transit | TLS between client and site |
| What the proxy sees | Method, URL, headers and body | Only the host and port |
| Proxy URL scheme | http:// | http:// (the tunnel carries TLS) |
| Typical targets | Legacy pages and internal tools | Almost every modern website |
| Proxonym ports | 8000 on the gateway, 3129 on datacenter | The same ports |
Benefits
Why teams choose HTTP proxies.
What changes for your jobs once HTTP proxies are part of the setup.
Works with every HTTP client
cURL, Python requests, Scrapy, Node.js, Go, PHP, Java and the major headless browsers all accept an HTTP proxy URL, so setup takes one line of configuration.
HTTPS stays encrypted
HTTPS requests travel through a CONNECT tunnel, and TLS runs directly between your client and the website, so page content cannot be read in transit.
Targeting in the username
Add -country-, -city-, -asn- or -session- to the username and every request follows those rules. One proxy URL can carry both location and session.
One URL for HTTP and HTTPS
The same proxy address handles http:// and https:// targets, so you configure it once and never maintain separate settings for each scheme.
How it works
Set up in three steps.
Same account, same credentials for every proxy type. Connection details live in your dashboard.
- 1
Set the proxy URL
Use http://USERNAME:[email protected]:8000 for residential and mobile, or the ip:port from your list for datacenter, ISP and dedicated proxies.
- 2
Send requests as usual
Plain HTTP requests are forwarded by the proxy. HTTPS requests open a CONNECT tunnel first, and your client negotiates TLS with the target through it.
- 3
Read gateway status codes
407 means bad credentials or a non-whitelisted IP, 402 an empty balance or expired plan, 429 the rate guard, 502 a failed peer worth retrying and 504 a target timeout.
Products
Proxy types that support it.
All of them work with the same account, credentials and dashboard. Pick by target and budget.
FAQ
Questions about HTTP proxies.
Still unsure? Our team helps you pick the right product and size.
Ask a proxy expertWhat is the difference between an HTTP and an HTTPS proxy?
The terms usually describe the traffic, not a different kind of proxy. The same HTTP proxy forwards plain HTTP requests directly and carries HTTPS through a CONNECT tunnel, with TLS negotiated between your client and the website. You use one proxy URL starting with http:// for both kinds of target.
Can the proxy read my HTTPS traffic?
No. For HTTPS targets, the proxy only sees the hostname and port in the CONNECT request. Everything inside the tunnel, including the full URL, headers, cookies and page content, is encrypted between your client and the website, so it cannot be read in transit.
Should I use HTTP or SOCKS5?
Use HTTP for web scraping and browser automation: every library supports it, and targeting works the same way on both protocols. Choose SOCKS5 when a tool only offers a SOCKS setting, when you need to proxy protocols other than HTTP or when you need UDP on a supported plan.
Why do I get a 407 error?
407 Proxy Authentication Required means the gateway did not accept your credentials. Check the username and password in your dashboard, make sure targeting parameters are spelled correctly and joined with dashes, and URL-encode special characters in the password. On datacenter plans, also confirm that your server IP is whitelisted.
Does HTTP/2 work through the proxy?
Yes, for HTTPS targets. The CONNECT tunnel carries whatever your client and the site negotiate inside TLS, including HTTP/2. The connection between your client and the gateway uses HTTP/1.1 for the CONNECT step, which every proxy-aware client handles automatically. HTTP/3 runs over UDP, so proxied browsers and clients typically use HTTP/2 instead.
One gateway. Millions of identities.
Pick a plan, pay with crypto and send your first request through Proxonym in minutes.
- Pay as you go
- Instant activation
- Crypto accepted
- 24/7 support