C# and .NET with AeonProxy proxies

Protocols

HTTP proxy for HTTP and HTTPS sites; SOCKS5 in .NET 6 and newer

Authentication

NetworkCredential on the WebProxy

Rotation

A new IP per connection (HttpClient pools its connections); a -sid- key keeps one IP for up to 60 minutes

Works with

Residential and mobile proxies

Before you start

• .NET 6 or newer (older versions have no SOCKS5 in HttpClient). Create a project with dotnet new console and put the code in Program.cs.
• Your proxy login and password from the Residential or Mobile page of the dashboard, and traffic on that product; a login without traffic gets 402.

HttpClient with a WebProxy

Point a WebProxy at port 7000 with an http:// address and give it the login and password as a NetworkCredential. HTTPS sites go through a CONNECT tunnel, so the address stays http://; an https:// proxy address makes .NET start TLS with the proxy, which fails.

using System.Net;

var proxy = new WebProxy("http://gate.aeonproxy.com:7000")
{
    Credentials = new NetworkCredential("LOGIN-cc-us", "PASSWORD"),
};
var handler = new HttpClientHandler { Proxy = proxy, UseProxy = true };
using var client = new HttpClient(handler) { Timeout = TimeSpan.FromSeconds(30) };

Console.WriteLine(await client.GetStringAsync("https://api.ipify.org"));

Create the client once and reuse it. It keeps a pool of connections, and each new one costs an extra round trip: .NET sends the proxy login only after the gateway answers 407.

Rotating or sticky

A rotating login gets a new IP for every connection, and pooled connections are reused, so requests in a row usually share one. PooledConnectionLifetime = TimeSpan.Zero on a SocketsHttpHandler opens a new connection for every request. With a -sid- key, every connection keeps the same IP until the -ttl- runs out (1 to 60 minutes).

Over the HTTP proxy, every new connection starts without the login and sends it after the gateway's 407, so a new connection per request costs an extra round trip each time; the gateway does not count those first tries as failed logins. A Proxy-Authorization request header does not save the round trip, because .NET does not send it on the CONNECT. SOCKS5 sends the login in its handshake, so for a new connection per request it is the quicker choice.

using System.Net;

// SOCKS5 sends the login in its handshake, so every new connection is accepted at once
static HttpClient NewClient(string login, bool newConnectionEachTime) => new(new SocketsHttpHandler
{
    Proxy = new WebProxy("socks5://gate.aeonproxy.com:7001") { Credentials = new NetworkCredential(login, "PASSWORD") },
    PooledConnectionLifetime = newConnectionEachTime ? TimeSpan.Zero : TimeSpan.FromMinutes(10),
    ConnectTimeout = TimeSpan.FromSeconds(30),
});

// rotating: a new connection for every request, so a new IP each time
using var rotating = NewClient("LOGIN-cc-us", newConnectionEachTime: true);
Console.WriteLine(await rotating.GetStringAsync("https://api.ipify.org"));
Console.WriteLine(await rotating.GetStringAsync("https://api.ipify.org"));

// sticky: one key keeps one IP for up to 30 minutes
var sid = Guid.NewGuid().ToString("N")[..8];
using var sticky = NewClient($"LOGIN-cc-us-sid-{sid}-ttl-30", newConnectionEachTime: false);
Console.WriteLine(await sticky.GetStringAsync("https://api.ipify.org"));
Console.WriteLine(await sticky.GetStringAsync("https://api.ipify.org"));

SOCKS5

Pass a socks5:// address to WebProxy (the host-and-port constructor builds HTTP proxies only). The login comes from the NetworkCredential, and .NET sends the site's name to the proxy, so DNS is resolved at the gateway.

using System.Net;

var proxy = new WebProxy("socks5://gate.aeonproxy.com:7001")
{
    Credentials = new NetworkCredential("LOGIN-cc-de", "PASSWORD"),
};
using var client = new HttpClient(new SocketsHttpHandler { Proxy = proxy });

Console.WriteLine(await client.GetStringAsync("https://api.ipify.org"));

If it does not work