Proxy HTTP
Un proxy que reenvía solicitudes HTTP y HTTPS entre un cliente y un servidor web.
Un proxy HTTP se sitúa entre tu aplicación y el servidor web. Tu aplicación envía la solicitud HTTP al proxy en lugar de directamente al destino. El proxy reenvía la solicitud, recibe la respuesta y se la devuelve a tu aplicación.
Para el tráfico HTTPS, los proxies HTTP usan un método llamado túnel CONNECT. Tu cliente envía una solicitud CONNECT al proxy con el nombre de host y el puerto de destino. El proxy establece un túnel TCP y todo el tráfico cifrado posterior pasa a través de él sin que el proxy pueda leerlo.
Los proxies HTTP son el tipo de proxy más compatible en lenguajes de programación, navegadores y herramientas de automatización. La librería requests de Python, fetch de Node.js, curl, Playwright, Puppeteer y Selenium admiten proxies HTTP de forma nativa.
El formato de URL estándar para configurar un proxy HTTP es: http://username:password@host:port. Para destinos HTTPS, la mayoría de los clientes usan automáticamente el túnel CONNECT a través del mismo endpoint de proxy HTTP.
Los proxies HTTP pueden opcionalmente inspeccionar y modificar solicitudes (forward proxies) o cachear respuestas (proxies de caché). Los proveedores de proxies para anonimato y scraping suelen operar como forward proxies transparentes: reenvían solicitudes sin modificarlas.
A proxy that reads what it forwards
An HTTP proxy sits inside the protocol it carries. For plain HTTP your client sends the whole URL in the request line rather than just the path, and the proxy uses that to decide where to forward it. The proxy can read the request, add or strip headers, cache the response and log the destination.
For HTTPS the arrangement changes. Your client issues a CONNECT request naming host and port, the proxy opens a TCP tunnel, and everything after that is encrypted end to end. The proxy sees the hostname in the CONNECT line and the bytes flowing through, and nothing else. That is why an HTTP proxy does not weaken TLS.
Authentication happens through a header. When credentials are missing or wrong the proxy answers 407 Proxy Authentication Required, which is distinct from 401 and comes from the proxy rather than the destination. Recognising which of the two you received tells you immediately where the failure is.
Because the proxy understands HTTP, it can also be selective in ways SOCKS cannot: routing by hostname, rewriting headers, applying rules per URL. Whether that is a feature or an intrusion depends on who is running it.
HTTP on our endpoints
Both product families accept HTTP, and the scheme in your client decides how the connection is made:
HTTP against residential and static
# Residential, targeting in the login
curl -x http://login_c_US:password@proxy.sotaproxy.com:10000 https://example.com
# Static address
curl -x http://login:password@your-ip:50100 https://example.com
# 407 means we rejected the credentials.
# 401 means the destination did.- HTTPS through an HTTP proxy uses CONNECT and stays encrypted end to end. Nobody in the middle reads it, including us.
- Resolution happens on our side, so an HTTP proxy does not leak your target list to your own resolver the way a misconfigured SOCKS client does.
- Most libraries default to HTTP proxying and need extra packages for SOCKS. Unless you need UDP or a non-HTTP protocol, HTTP is the simpler choice.
- Keep the proxy scheme http even when the target is https. The scheme describes how you talk to us, not how we talk to the destination.
HTTP proxy misconceptions
It does not decrypt your HTTPS
CONNECT builds a tunnel. Interception requires a certificate your client trusts, which is a corporate arrangement rather than how a public proxy works.
https:// in the proxy URL is not required
Writing http:// as the proxy scheme while fetching an https:// page is correct and confuses almost everyone once.
407 is not the site rejecting you
It is us, and it means the login string did not parse. The destination never saw the request.
It is not less anonymous than SOCKS
Our HTTP proxies send no forwarding headers. The exit address is what the site judges either way.
Términos relacionados
Ver esto en práctica
¿Listo para usar proxy http?
SotaProxy te da acceso a proxies residenciales rotativos, móviles, de centro de datos e ISP. Sin compromiso mínimo.
Empezar