<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Edward Walton</title>
    <description>The latest articles on DEV Community by Edward Walton (@minglai_lai_0ca58fef9df12).</description>
    <link>https://dev.to/minglai_lai_0ca58fef9df12</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4214171%2F4b68099a-f324-4bf3-87c7-8639c991212c.jpg</url>
      <title>DEV Community: Edward Walton</title>
      <link>https://dev.to/minglai_lai_0ca58fef9df12</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/minglai_lai_0ca58fef9df12"/>
    <language>en</language>
    <item>
      <title>Free vs paid residential proxies: what does a usable result cost?</title>
      <dc:creator>Edward Walton</dc:creator>
      <pubDate>Wed, 18 Nov 2026 02:20:03 +0000</pubDate>
      <link>https://dev.to/minglai_lai_0ca58fef9df12/free-vs-paid-residential-proxies-what-does-a-usable-result-cost-40o9</link>
      <guid>https://dev.to/minglai_lai_0ca58fef9df12/free-vs-paid-residential-proxies-what-does-a-usable-result-cost-40o9</guid>
      <description>&lt;p&gt;A free residential proxy can be enough for a disposable experiment. For a job that runs every morning, a failed connection means missing data, retries, or someone spending time fixing the pipeline.&lt;/p&gt;

&lt;p&gt;Before comparing plans, define what a completed job looks like. For a price monitor, that might mean receiving the correct product, currency, and price before a deadline. You can then compare free and paid options against the same requirement.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check what "free" includes
&lt;/h2&gt;

&lt;p&gt;A public proxy list gives you addresses to try. The label "residential" may be inaccurate, and a working address tells you little about its operator or how the connection was obtained.&lt;/p&gt;

&lt;p&gt;A commercial trial gives you limited access to a provider's service. It may cost money. Check its traffic allowance, expiry, available locations, and any renewal terms before starting.&lt;/p&gt;

&lt;p&gt;With a paid service, look for documented authentication, billing rules, and a support contact. Ask how the IPs are sourced and, where participant devices are involved, how their owners agree to take part. Payment creates a supplier relationship; you still need to evaluate that supplier.&lt;/p&gt;

&lt;p&gt;For learning proxy configuration, use a throwaway request to a public page you can safely discard. Keep account credentials and private data out of an experiment with an unknown operator.&lt;/p&gt;

&lt;h2&gt;
  
  
  Keep certificate checks enabled
&lt;/h2&gt;

&lt;p&gt;An HTTP proxy can carry an HTTPS request using a CONNECT tunnel. Your client then establishes TLS with the destination. With normal certificate validation, the proxy cannot simply read or rewrite the encrypted page. The &lt;a href="https://everything.curl.dev/usingcurl/proxies/http.html" rel="noopener noreferrer"&gt;curl documentation&lt;/a&gt; explains this connection.&lt;/p&gt;

&lt;p&gt;The operator still handles the connection and can observe metadata such as the destination hostname used in CONNECT. Unencrypted HTTP exposes the request and response content.&lt;/p&gt;

&lt;p&gt;Avoid a service that asks you to disable certificate checks or install an unfamiliar root certificate just to make ordinary browsing work. Those changes alter the trust assumptions behind HTTPS.&lt;/p&gt;

&lt;p&gt;Also check the connection to the proxy itself. An &lt;code&gt;https://&lt;/code&gt; proxy URL in curl enables TLS on that connection, separately from HTTPS to the destination. See &lt;a href="https://everything.curl.dev/usingcurl/proxies/https.html" rel="noopener noreferrer"&gt;curl's HTTPS proxy guide&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Run the same small job through each option
&lt;/h2&gt;

&lt;p&gt;Choose a workload you are authorized to run. For example, retrieve a small set of public product pages where collection is permitted. Keep the client, requested region, concurrency, timeout, and retry limit consistent across tests. Follow the destination's access rules and rate limits.&lt;/p&gt;

&lt;p&gt;Decide which fields must be present before counting a result. HTTP 200 alone doesn't confirm that your parser received the expected product page. Inspect the content and reject incomplete records.&lt;/p&gt;

&lt;p&gt;Record enough detail to explain failures:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Total attempts, usable records, duplicates, and incomplete records as separate counts.&lt;/li&gt;
&lt;li&gt;Connection failures separately from HTTP responses and parsing errors.&lt;/li&gt;
&lt;li&gt;Completion time, including retries, plus transferred bytes and billed traffic.&lt;/li&gt;
&lt;li&gt;Time spent configuring the service or investigating failures.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A successful IP-check request establishes that one connection worked. Run the actual parser, too. If the job uses a browser, include its normal page resources when measuring traffic.&lt;/p&gt;

&lt;p&gt;When the destination returns &lt;a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/429" rel="noopener noreferrer"&gt;429 Too Many Requests&lt;/a&gt;, reduce the request rate and respect &lt;code&gt;Retry-After&lt;/code&gt; when supplied. Buying another proxy doesn't resolve an application that exceeds the service's limits.&lt;/p&gt;

&lt;h2&gt;
  
  
  Put your time into the cost calculation
&lt;/h2&gt;

&lt;p&gt;For a batch with usable output, calculate:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Cost per usable record =
  (proxy charges + attributable compute + engineering time cost)
  / usable records
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Suppose two runs each produce 1,000 usable records. The free option needs 45 minutes of troubleshooting. The paid option needs 10 minutes and costs $6 in proxy traffic. At an assumed engineering cost of $30 per hour, the totals are $22.50 and $11, excluding compute.&lt;/p&gt;

&lt;p&gt;Those are hypothetical inputs, not provider benchmarks. Replace them with your own measurements. For a one-off experiment where you have time to spare, the free option may still suit your budget.&lt;/p&gt;

&lt;p&gt;For recurring work, repeat the test at different times. One short run cannot establish whether the required location will remain available or whether the batch will consistently meet its deadline.&lt;/p&gt;

&lt;h2&gt;
  
  
  Choose the smallest plan that answers your question
&lt;/h2&gt;

&lt;p&gt;Once you know the workload, a small commercial trial can help you measure billed traffic and test the provider's support before a larger purchase. Check whether failed transfers consume the allowance and whether unused traffic expires.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.ipnivo.com/" rel="noopener noreferrer"&gt;IPnivo&lt;/a&gt; is one option to include in that comparison. Its Residential Proxies use rotating IPs, while Static Residential Proxies provide fixed IPs. Choose the type your application needs, then use the same workload and acceptance rules to evaluate it.&lt;/p&gt;

&lt;p&gt;If the job works through your existing connection and needs no particular exit network, test that baseline before adding a proxy subscription. Its completion rate and operating cost give you another useful comparison.&lt;/p&gt;

&lt;p&gt;Disclosure: This article adapts an IPnivo company blog post.&lt;/p&gt;

</description>
      <category>networking</category>
      <category>webdev</category>
      <category>beginners</category>
      <category>security</category>
    </item>
    <item>
      <title>Types of proxies: a developer's guide to the labels</title>
      <dc:creator>Edward Walton</dc:creator>
      <pubDate>Thu, 12 Nov 2026 02:54:34 +0000</pubDate>
      <link>https://dev.to/minglai_lai_0ca58fef9df12/types-of-proxies-a-developers-guide-to-the-labels-2pfb</link>
      <guid>https://dev.to/minglai_lai_0ca58fef9df12/types-of-proxies-a-developers-guide-to-the-labels-2pfb</guid>
      <description>&lt;p&gt;Suppose your test worker needs a fixed address for an API allowlist. A rotating residential service could offer thousands of exits and still miss that requirement.&lt;/p&gt;

&lt;p&gt;Proxy names become easier to read when you split them into separate decisions: where traffic exits, when that IP changes, and how your client connects. A single service can have several labels because each describes a different property.&lt;/p&gt;

&lt;h2&gt;
  
  
  Are you sending requests or receiving them?
&lt;/h2&gt;

&lt;p&gt;A forward proxy handles outbound connections for a client. You configure your browser or worker to contact it, and it connects to the destination.&lt;/p&gt;

&lt;p&gt;A reverse proxy receives traffic for a service you operate. It can send incoming requests to different backends, distribute load, and cache responses. The &lt;a href="https://docs.nginx.com/nginx/admin-guide/web-server/reverse-proxy" rel="noopener noreferrer"&gt;NGINX reverse proxy documentation&lt;/a&gt; shows this server-side setup.&lt;/p&gt;

&lt;p&gt;If you're choosing an exit for a script, you're usually evaluating forward proxies. If you're putting a gateway in front of your application, you're designing a reverse proxy deployment.&lt;/p&gt;

&lt;h2&gt;
  
  
  Choose the exit network
&lt;/h2&gt;

&lt;p&gt;Commercial proxy catalogs commonly group addresses into four sources:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Datacenter proxies use IPs associated with hosting or cloud infrastructure. Try these for a permitted workload that has no requirement for a consumer or cellular exit.&lt;/li&gt;
&lt;li&gt;Residential proxies use IPs associated with consumer internet connections. They can help when testing how your own service behaves for visitors on those networks.&lt;/li&gt;
&lt;li&gt;ISP proxies, often sold as static residential proxies, generally combine ISP-associated addresses with server infrastructure. Ask how the service is hosted and how addresses are assigned; the label doesn't establish a household connection.&lt;/li&gt;
&lt;li&gt;Mobile proxies exit through cellular carrier networks. They're relevant when carrier routing matters, but they don't reproduce a phone's browser, operating system, or screen size.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;These are descriptions of the exit network. Speed, location accuracy, and availability still need testing. An IP-intelligence database can also classify proxy activity separately from network origin; &lt;a href="https://dev.maxmind.com/geoip/docs/databases/anonymous-ip/binary/" rel="noopener noreferrer"&gt;MaxMind documents these distinctions&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Decide how long the address must last
&lt;/h2&gt;

&lt;p&gt;For an allowlisted API client, ask for an address that remains assigned for the required period, along with its replacement policy. Both datacenter and ISP services can offer fixed exits.&lt;/p&gt;

&lt;p&gt;Rotation is useful when a test needs observations from several addresses. Check the trigger: a new request, a timer, or an explicit rotation operation. A rotating endpoint can select an address already used earlier, so verify whether the service promises a different IP.&lt;/p&gt;

&lt;p&gt;IP persistence and application state are separate. Your client still needs to maintain cookies or tokens across requests. Keeping an address fixed doesn't preserve a login by itself.&lt;/p&gt;

&lt;h2&gt;
  
  
  Match the protocol to your application
&lt;/h2&gt;

&lt;p&gt;HTTP proxies understand HTTP requests. For an HTTPS destination, a common setup uses &lt;code&gt;CONNECT&lt;/code&gt; to open a tunnel, followed by TLS between the client and destination. Keep certificate validation enabled.&lt;/p&gt;

&lt;p&gt;Check what a provider means by "HTTPS proxy." Supporting HTTPS destinations through a tunnel and accepting TLS connections to the proxy are separate capabilities. In curl, an &lt;code&gt;https://&lt;/code&gt; proxy URL selects TLS on the client-to-proxy connection. The &lt;a href="https://everything.curl.dev/transfers/conn/proxies.html" rel="noopener noreferrer"&gt;curl proxy overview&lt;/a&gt; explains both connection layers.&lt;/p&gt;

&lt;p&gt;SOCKS5 can carry traffic beyond HTTP. &lt;a href="https://www.rfc-editor.org/rfc/rfc1928.html" rel="noopener noreferrer"&gt;RFC 1928&lt;/a&gt; defines TCP operations and UDP association, but your client and proxy service must implement the features you need. SOCKS5 support alone doesn't tell you whether the connection is encrypted.&lt;/p&gt;

&lt;p&gt;DNS handling also depends on the client. With curl, &lt;code&gt;socks5://&lt;/code&gt; resolves the destination locally; &lt;code&gt;socks5h://&lt;/code&gt; sends its hostname to the proxy. Check the equivalent option in your library rather than assuming every SOCKS5 connection resolves names remotely. See the &lt;a href="https://everything.curl.dev/usingcurl/proxies/socks.html" rel="noopener noreferrer"&gt;curl SOCKS guide&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Read access and privacy labels carefully
&lt;/h2&gt;

&lt;p&gt;Public proxies allow broad access. Shared services let multiple customers use resources. "Private" often indicates restricted access, so ask separately whether the exit IP or capacity is shared.&lt;/p&gt;

&lt;p&gt;"Anonymous" doesn't tell you what the operator logs or what identifiers your application sends. Evaluate those details before sending sensitive traffic through an unfamiliar service.&lt;/p&gt;

&lt;p&gt;"Transparent" has multiple meanings. In network architecture, it can describe interception without an explicit client proxy setting, as &lt;a href="https://www.rfc-editor.org/rfc/rfc9110.html#section-3.7" rel="noopener noreferrer"&gt;RFC 9110 explains&lt;/a&gt;. Some proxy lists instead use it for services that expose client information. Ask which behavior is intended.&lt;/p&gt;

&lt;h2&gt;
  
  
  Turn the labels into a testable requirement
&lt;/h2&gt;

&lt;p&gt;For the allowlisted worker, an initial specification might be:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Role: forward proxy
Exit network: datacenter acceptable
IP lifetime: fixed throughout the API allowlist period
Protocol: compatible with the worker's HTTPS requests
Access: authenticated; confirm whether the exit is shared
Failure policy: notify before replacing the assigned IP
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Run a representative permitted job through the actual worker. Confirm its visible exit, validate the returned data, and record elapsed time and retries. Compare total spend per usable result, including billed traffic from failed attempts.&lt;/p&gt;

&lt;p&gt;For collection work, follow the destination's access rules and rate limits. When requests fail, inspect authentication, protocol settings, and the response before buying a different proxy category. A successful connection to an IP-check page establishes much less than a completed application workflow.&lt;/p&gt;

</description>
      <category>networking</category>
      <category>webdev</category>
      <category>beginners</category>
      <category>security</category>
    </item>
    <item>
      <title>Residential proxy vs VPN: what should your app use?</title>
      <dc:creator>Edward Walton</dc:creator>
      <pubDate>Mon, 09 Nov 2026 01:45:47 +0000</pubDate>
      <link>https://dev.to/minglai_lai_0ca58fef9df12/residential-proxy-vs-vpn-what-should-your-app-use-45g8</link>
      <guid>https://dev.to/minglai_lai_0ca58fef9df12/residential-proxy-vs-vpn-what-should-your-app-use-45g8</guid>
      <description>&lt;p&gt;A browser checking regional prices may need a different exit address while the rest of the laptop keeps its usual connection. Someone using several apps on hotel Wi-Fi may want an encrypted tunnel for all of them.&lt;/p&gt;

&lt;p&gt;A residential proxy routes configured requests through an IP associated with a residential network. A VPN encrypts traffic between your device and its server, according to the routes its client includes.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check which applications will use the route
&lt;/h2&gt;

&lt;p&gt;For a script or browser profile, a proxy gives you a convenient configuration point: supply the endpoint and authentication in that client. Other applications can continue using their existing routes.&lt;/p&gt;

&lt;p&gt;That depends on the application honoring the configuration. Setting a system proxy does not establish that every process uses it.&lt;/p&gt;

&lt;p&gt;A device VPN changes network routing more broadly, but exclusions matter. With split tunneling, some destinations or apps can stay outside the tunnel. Microsoft's &lt;a href="https://learn.microsoft.com/en-us/windows/security/operating-system-security/network-security/vpn/vpn-routing" rel="noopener noreferrer"&gt;VPN routing documentation&lt;/a&gt; describes how included routes determine where traffic goes.&lt;/p&gt;

&lt;p&gt;For a company dashboard, use the access profile your IT team provides. Buying a consumer VPN does not grant access to a private company network.&lt;/p&gt;

&lt;h2&gt;
  
  
  Separate encryption from the exit address
&lt;/h2&gt;

&lt;p&gt;An HTTPS request can stay encrypted through a proxy. With a normal &lt;a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Methods/CONNECT" rel="noopener noreferrer"&gt;HTTP CONNECT tunnel&lt;/a&gt;, TLS protects content between the application and the destination, provided certificate validation succeeds and the connection is not intercepted.&lt;/p&gt;

&lt;p&gt;The connection to the proxy has its own transport. An &lt;code&gt;https://&lt;/code&gt; proxy endpoint adds TLS on that hop; an &lt;code&gt;http://&lt;/code&gt; endpoint does not. Supporting HTTPS websites and accepting encrypted connections to the proxy are separate capabilities, as the &lt;a href="https://everything.curl.dev/usingcurl/proxies/https.html" rel="noopener noreferrer"&gt;curl HTTPS proxy documentation&lt;/a&gt; explains. SOCKS5 also supplies no traffic encryption by itself.&lt;/p&gt;

&lt;p&gt;A VPN protects traffic inside its tunnel, which ends at the VPN server. Plain HTTP can still leave that server unencrypted. Use HTTPS for websites, and evaluate the operator's logging policy whichever service you use.&lt;/p&gt;

&lt;h2&gt;
  
  
  Decide whether you need a residential exit
&lt;/h2&gt;

&lt;p&gt;For a regional test of your own website, specify the country and client behavior you need to reproduce. A VPN with a suitable exit may handle a manual check. A proxy can be easier to configure independently for each test worker. A residential address is useful only when that network type matters to the test.&lt;/p&gt;

&lt;p&gt;Check exit persistence separately. Some proxy plans rotate addresses; others offer temporary persistence or a fixed address. Reconnecting a VPN can also change its exit. For a test spanning several pages, preserve cookies in the client and verify whether the IP remains suitable. A fixed address does not keep a login alive.&lt;/p&gt;

&lt;p&gt;For data collection, follow the destination's access rules and collect only public or authorized data. Changing an IP leaves account logins and browser identifiers available to the site.&lt;/p&gt;

&lt;h2&gt;
  
  
  Verify the client before running a job
&lt;/h2&gt;

&lt;p&gt;Use an IP endpoint such as &lt;a href="https://www.ipify.org/" rel="noopener noreferrer"&gt;ipify&lt;/a&gt; to inspect a request's visible exit. Replace the example proxy with your endpoint; authentication is omitted here.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# Without a curl proxy; an active VPN can still carry this request.&lt;/span&gt;
curl &lt;span class="nt"&gt;-q&lt;/span&gt; &lt;span class="nt"&gt;--proxy&lt;/span&gt; &lt;span class="s2"&gt;""&lt;/span&gt; &lt;span class="nt"&gt;--connect-timeout&lt;/span&gt; 10 &lt;span class="nt"&gt;--max-time&lt;/span&gt; 20 &lt;span class="s2"&gt;"https://api.ipify.org?format=json"&lt;/span&gt;

&lt;span class="c"&gt;# Through an HTTP proxy that supports HTTPS tunneling.&lt;/span&gt;
curl &lt;span class="nt"&gt;-q&lt;/span&gt; &lt;span class="nt"&gt;--proxy&lt;/span&gt; &lt;span class="s2"&gt;"http://proxy.example.com:8080"&lt;/span&gt; &lt;span class="nt"&gt;--noproxy&lt;/span&gt; &lt;span class="s2"&gt;""&lt;/span&gt; &lt;span class="nt"&gt;--connect-timeout&lt;/span&gt; 10 &lt;span class="nt"&gt;--max-time&lt;/span&gt; 20 &lt;span class="s2"&gt;"https://api.ipify.org?format=json"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Here, &lt;code&gt;-q&lt;/code&gt; skips curl's default configuration file. The empty &lt;code&gt;--proxy&lt;/code&gt; disables its proxy selection, while &lt;code&gt;--noproxy ""&lt;/code&gt; clears bypass rules for the explicit proxy request. See the &lt;a href="https://curl.se/docs/manpage.html" rel="noopener noreferrer"&gt;curl manual&lt;/a&gt; for these options.&lt;/p&gt;

&lt;p&gt;Compare the results with your intended exits. This endpoint reports IPv4; it does not establish IPv6 routing, DNS behavior, or how another application connects. Repeat the check inside the browser or worker that will perform the task.&lt;/p&gt;

&lt;p&gt;For SOCKS5 in curl, &lt;code&gt;socks5://&lt;/code&gt; resolves the destination locally; &lt;a href="https://everything.curl.dev/usingcurl/proxies/socks.html" rel="noopener noreferrer"&gt;&lt;code&gt;socks5h://&lt;/code&gt; delegates that lookup to the proxy&lt;/a&gt;. Check the equivalent setting in your actual client.&lt;/p&gt;

&lt;p&gt;Then run one representative permitted task. Measure usable output and elapsed time, including retries. Proxy billing may depend on transferred data or assigned IPs, whereas VPN subscriptions commonly charge by period or user. Estimate the cost of completing the workload; protocol names alone cannot predict speed or cost.&lt;/p&gt;

&lt;h2&gt;
  
  
  Use both when the routes require it
&lt;/h2&gt;

&lt;p&gt;A laptop VPN can carry a research application's connection to a residential proxy. If that connection is included in the tunnel, it travels through the VPN server before reaching the proxy, and the website sees the proxy's exit.&lt;/p&gt;

&lt;p&gt;Check split-tunnel exclusions before assuming that path. When debugging, verify the VPN route first, then add the application's proxy configuration and check the resulting exit again.&lt;/p&gt;

</description>
      <category>networking</category>
      <category>security</category>
      <category>privacy</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Are proxies safe? Five checks before you trust one</title>
      <dc:creator>Edward Walton</dc:creator>
      <pubDate>Wed, 04 Nov 2026 03:27:48 +0000</pubDate>
      <link>https://dev.to/minglai_lai_0ca58fef9df12/are-proxies-safe-five-checks-before-you-trust-one-p0a</link>
      <guid>https://dev.to/minglai_lai_0ca58fef9df12/are-proxies-safe-five-checks-before-you-trust-one-p0a</guid>
      <description>&lt;p&gt;A different public IP tells you something about a request's route. It tells you very little about who handled the traffic or what they recorded.&lt;/p&gt;

&lt;p&gt;Proxies can support regional testing and authorized data collection. Before adding one to a browser or background job, check the operator, the encryption, and the behavior of the application that will use it.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Find out who handles your traffic
&lt;/h2&gt;

&lt;p&gt;Look for an identifiable operator and a privacy policy that explains what gets logged. Check whether those records include your source IP, destinations, timestamps, or request contents, and how long the service retains them.&lt;/p&gt;

&lt;p&gt;For residential networks, ask how participants authorize the use of their connections. A large IP pool says nothing about that process.&lt;/p&gt;

&lt;p&gt;An unknown endpoint from a public list gives you little basis for trusting its operator. Keep account credentials and confidential data away from it. A free trial from an identifiable business offers more information to evaluate, although paying for access does not establish good security practices either.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Check where encryption starts and ends
&lt;/h2&gt;

&lt;p&gt;An HTTP proxy can carry an HTTPS connection through a &lt;a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Methods/CONNECT" rel="noopener noreferrer"&gt;CONNECT tunnel&lt;/a&gt;. In a normal tunnel, TLS runs between your client and the destination website. The proxy can observe connection metadata, including the requested host and port, but generally cannot read the encrypted page contents or passwords.&lt;/p&gt;

&lt;p&gt;The proxy connection has its own transport:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;http://&lt;/code&gt; connects to the proxy without TLS. HTTPS destination content can still remain encrypted inside the tunnel.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;https://&lt;/code&gt; uses TLS to reach the proxy, protecting that hop as well.&lt;/li&gt;
&lt;li&gt;SOCKS5 does not provide traffic encryption by itself. An application can still use HTTPS through it.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The &lt;a href="https://everything.curl.dev/usingcurl/proxies/https.html" rel="noopener noreferrer"&gt;curl HTTPS proxy documentation&lt;/a&gt; explains this distinction. Check the endpoint scheme your client actually uses; a service advertising HTTPS support may simply mean it can tunnel HTTPS destinations.&lt;/p&gt;

&lt;p&gt;Keep certificate validation enabled. Installing an operator's root certificate can enable &lt;a href="https://docs.mitmproxy.org/stable/concepts/certificates/" rel="noopener noreferrer"&gt;TLS inspection&lt;/a&gt;, allowing it to decrypt traffic. Treat that as a separate trust decision. curl documents &lt;a href="https://curl.se/docs/sslcerts.html" rel="noopener noreferrer"&gt;certificate verification for both destinations and HTTPS proxies&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Test one request without sensitive data
&lt;/h2&gt;

&lt;p&gt;Use a public IP endpoint before trying an authenticated workflow. This example assumes an HTTP proxy that supports CONNECT. Replace the example host and port with your own settings:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl &lt;span class="nt"&gt;-q&lt;/span&gt; &lt;span class="nt"&gt;--proxy&lt;/span&gt; &lt;span class="s2"&gt;"http://proxy.example.com:8080"&lt;/span&gt; &lt;span class="nt"&gt;--noproxy&lt;/span&gt; &lt;span class="s2"&gt;""&lt;/span&gt; &lt;span class="nt"&gt;--connect-timeout&lt;/span&gt; 10 &lt;span class="nt"&gt;--max-time&lt;/span&gt; 20 &lt;span class="s2"&gt;"https://api.ipify.org?format=json"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The &lt;a href="https://www.ipify.org/" rel="noopener noreferrer"&gt;ipify endpoint&lt;/a&gt; returns an IP in JSON. Compare it with the expected proxy exit. If the service rotates exits, compare against its documented behavior instead of expecting one permanent address.&lt;/p&gt;

&lt;p&gt;Here, &lt;code&gt;-q&lt;/code&gt; skips the default curl configuration file, and &lt;code&gt;--noproxy ""&lt;/code&gt; clears bypass rules for this invocation. The timeouts bound the test. These options are described in the &lt;a href="https://curl.se/docs/manpage.html" rel="noopener noreferrer"&gt;curl manual&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Authentication is omitted from the example. Configure it using your client's supported credential handling, and keep secrets out of shared commands and diagnostic output.&lt;/p&gt;

&lt;p&gt;A successful response confirms this request's exit. Run the equivalent check inside your actual browser or worker before trusting its routing.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Check DNS and traffic outside that request
&lt;/h2&gt;

&lt;p&gt;A browser proxy setting may leave another application connecting directly. Review each client separately, including its bypass rules and any fallback to direct connections.&lt;/p&gt;

&lt;p&gt;DNS behavior also depends on the client. In curl, &lt;code&gt;socks5://&lt;/code&gt; resolves the destination hostname locally; &lt;a href="https://everything.curl.dev/usingcurl/proxies/socks.html" rel="noopener noreferrer"&gt;&lt;code&gt;socks5h://&lt;/code&gt; asks the proxy to resolve it&lt;/a&gt;. That setting applies to the destination lookup for that request, not every DNS lookup on the machine.&lt;/p&gt;

&lt;p&gt;For browser workflows, check WebRTC behavior separately if exposing network addresses would matter. An ordinary HTTP request cannot establish what WebRTC does.&lt;/p&gt;

&lt;p&gt;Changing the exit address also leaves cookies and account logins intact. A site can still associate activity with a signed-in account.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Investigate failures before adding real work
&lt;/h2&gt;

&lt;p&gt;If certificate verification fails, inspect the hostname, certificate chain, and trust configuration. Do not add &lt;code&gt;--insecure&lt;/code&gt; just to obtain a successful response.&lt;/p&gt;

&lt;p&gt;If a destination presents a CAPTCHA or rejects the exit, investigate its response and the address's reputation. Rejection alone does not demonstrate that your source IP leaked. Pause automated requests while checking access rules and the failed operation.&lt;/p&gt;

&lt;p&gt;Record the client version, proxy scheme, observed exit, and any error. Then test the permitted workflow with non-sensitive inputs. For data collection, inspect the returned content as well as the status code: a response can contain a challenge page instead of the data your job expects.&lt;/p&gt;

</description>
      <category>security</category>
      <category>privacy</category>
      <category>networking</category>
      <category>webdev</category>
    </item>
    <item>
      <title>TorrentGalaxy proxy lists: a developer's guide to checking access</title>
      <dc:creator>Edward Walton</dc:creator>
      <pubDate>Mon, 02 Nov 2026 02:02:27 +0000</pubDate>
      <link>https://dev.to/minglai_lai_0ca58fef9df12/torrentgalaxy-proxy-lists-a-developers-guide-to-checking-access-ckb</link>
      <guid>https://dev.to/minglai_lai_0ca58fef9df12/torrentgalaxy-proxy-lists-a-developers-guide-to-checking-access-ckb</guid>
      <description>&lt;p&gt;A "working" label on a TorrentGalaxy proxy list may mean only that the homepage responded. Search could still be broken, or the address could lead to an unrelated site. Before trying another domain, save the response and note what failed so you can compare the results.&lt;/p&gt;

&lt;h2&gt;
  
  
  Separate the mirror from the proxy configuration
&lt;/h2&gt;

&lt;p&gt;A TorrentGalaxy mirror is another website claiming to carry TGx listings. A forward proxy is a service configured in your browser or application that routes requests through another server. Opening a mirror URL leaves your other applications' proxy settings untouched.&lt;/p&gt;

&lt;h2&gt;
  
  
  Start with one HTTP request
&lt;/h2&gt;

&lt;p&gt;Start with a header request to an address you're allowed to inspect:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl &lt;span class="nt"&gt;-q&lt;/span&gt; &lt;span class="nt"&gt;--silent&lt;/span&gt; &lt;span class="nt"&gt;--show-error&lt;/span&gt; &lt;span class="nt"&gt;--head&lt;/span&gt; &lt;span class="nt"&gt;--connect-timeout&lt;/span&gt; 5 &lt;span class="nt"&gt;--max-time&lt;/span&gt; 15 &lt;span class="s2"&gt;"https://example.com/"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Replace &lt;code&gt;example.com&lt;/code&gt; with the host you're checking. In Windows PowerShell, use &lt;code&gt;curl.exe&lt;/code&gt; if &lt;code&gt;curl&lt;/code&gt; resolves to a PowerShell alias.&lt;/p&gt;

&lt;p&gt;These &lt;a href="https://curl.se/docs/manpage.html" rel="noopener noreferrer"&gt;curl options&lt;/a&gt; skip your default configuration file and allow five seconds for connection setup, with a fifteen-second limit for the whole request. Certificate verification stays enabled. The command leaves redirects for you to inspect, so check any &lt;code&gt;Location&lt;/code&gt; destination before following it.&lt;/p&gt;

&lt;p&gt;HEAD returns headers without testing search or page scripts. Some servers also handle it differently from a normal page request. Confirm the behavior in your browser before deciding that a failed HEAD check means the site is offline.&lt;/p&gt;

&lt;h2&gt;
  
  
  Record where the check failed
&lt;/h2&gt;

&lt;p&gt;Save curl's error output and, if a server responds, its HTTP status. The &lt;a href="https://everything.curl.dev/cmdline/exitcode.html" rel="noopener noreferrer"&gt;curl exit codes&lt;/a&gt; help identify problems such as failed name resolution or a timeout. The HTTP status comes from the server that answered.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F6zkjf5vgrled0l8fy0jk.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F6zkjf5vgrled0l8fy0jk.png" alt=" " width="800" height="560"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;A &lt;code&gt;403&lt;/code&gt; means the responding server refused the request; the status alone doesn't explain why. Even a &lt;code&gt;200&lt;/code&gt; needs a closer look, since a parking page can return it. Check the page's content and search function.&lt;/p&gt;

&lt;p&gt;Keep the URL and client the same when comparing connections, and record which network you used. A different result helps narrow the problem, though it won't identify the responsible network component on its own.&lt;/p&gt;

&lt;p&gt;You can keep the record short:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;URL and timestamp, including time zone:
Network and configured proxy, if any:
curl error or HTTP status:
Redirect destination:
Browser search/listing result:
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Remove credentials and session cookies before sharing the record.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check page identity before trusting its contents
&lt;/h2&gt;

&lt;p&gt;A familiar logo doesn't tell you who runs a mirror. A valid HTTPS certificate has limits too: Let's Encrypt explains that &lt;a href="https://letsencrypt.org/2015/10/29/phishing-and-malware.html" rel="noopener noreferrer"&gt;a domain-validated certificate does not establish a site's safety&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Leave pages that demand an unfamiliar installer, browser extension, or notification permission before you can continue. Get software from its publisher, and add unexpected redirects to your check record.&lt;/p&gt;

&lt;h2&gt;
  
  
  Test the download client separately
&lt;/h2&gt;

&lt;p&gt;When your browser passes a magnet link to a download client, that client uses its own network settings. The &lt;a href="https://www.bittorrent.org/beps/bep_0003.html" rel="noopener noreferrer"&gt;BitTorrent specification&lt;/a&gt; describes the separate roles of the web page, torrent metadata, tracker, and downloading peers. A listing can load even when the client cannot exchange file pieces.&lt;/p&gt;

&lt;p&gt;Try a publisher-provided torrent, such as one from &lt;a href="https://ubuntu.com/download/alternative-downloads" rel="noopener noreferrer"&gt;Ubuntu's alternative downloads&lt;/a&gt;, to check the client without relying on a TGx mirror. If that download works, look at the original torrent's peers and metadata. If both stall, check the client's connection settings and error messages before trying more mirror addresses.&lt;/p&gt;

&lt;h2&gt;
  
  
  When a residential proxy belongs in the test
&lt;/h2&gt;

&lt;p&gt;For authorized web tests that need a residential exit, I'd include &lt;a href="https://www.ipnivo.com/" rel="noopener noreferrer"&gt;IPnivo&lt;/a&gt; in the options to compare. It offers rotating and static residential proxies with HTTP(S) and SOCKS5 support. Choose the location and session behavior your test needs, then record the exit you used.&lt;/p&gt;

&lt;p&gt;Before configuring a torrent client, check the provider's usage terms and P2P policy. HTTP(S) or SOCKS5 support alone doesn't tell you whether torrent traffic is permitted.&lt;/p&gt;

</description>
      <category>networking</category>
      <category>debugging</category>
      <category>tutorial</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Instagram feedback_required: a developer's troubleshooting checklist</title>
      <dc:creator>Edward Walton</dc:creator>
      <pubDate>Thu, 29 Oct 2026 03:39:54 +0000</pubDate>
      <link>https://dev.to/minglai_lai_0ca58fef9df12/instagram-feedbackrequired-a-developers-troubleshooting-checklist-1lgm</link>
      <guid>https://dev.to/minglai_lai_0ca58fef9df12/instagram-feedbackrequired-a-developers-troubleshooting-checklist-1lgm</guid>
      <description>&lt;p&gt;&lt;strong&gt;Read the response before retrying&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The error name alone doesn't establish an IP ban or tell you when access will return. Save any accompanying explanation, especially feedback_message, and check for verification requests or feature restrictions in Instagram's official interface.&lt;/p&gt;

&lt;p&gt;If you're using an unofficial client, keep its exception names intact. For example, &lt;a href="https://subzeroid.github.io/instagrapi/3.2.0/exceptions/" rel="noopener noreferrer"&gt;instagrapi documents&lt;/a&gt; `&lt;br&gt;
FeedbackRequired and ChallengeRequired separately. Include the exact exception when reporting a problem to a maintainer.&lt;/p&gt;

&lt;p&gt;Pause the failing operation while you investigate. An account notice with a review option or waiting instruction gives you a more specific next step than the generic error does.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Find the boundary of the failure&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Use the same account and compare one variable at a time. You don't need to try every combination.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F0t9t5xrvris8l6lt6zra.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F0t9t5xrvris8l6lt6zra.png" alt=" " width="800" height="566"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;A connection comparison narrows the investigation. Switching from Wi-Fi to mobile data changes the route as well as the exit IP, so success on one connection doesn't identify the precise cause.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Make the smallest relevant change&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;For a browser-only failure, update the browser first. If the problem persists, clear Instagram's site data and sign in again. You can leave unrelated browsing data alone.&lt;/p&gt;

&lt;p&gt;On Android, start with Instagram's cache. Clearing storage is a separate step that removes app data. On iPhone, consider reinstalling if the problem remains confined to the app after updating it.&lt;/p&gt;

&lt;p&gt;Before any step that signs you out or deletes local data, check your recovery access and two-factor authentication method, and save local drafts.&lt;/p&gt;

&lt;p&gt;Then test the original operation once, provided no restriction tells you to wait. For a failed publication or comment, check whether it already appeared before submitting it again. Once it works, stop changing settings.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Keep a failed job from replaying completed work&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;In a worker or scheduled integration, record the failed operation separately from work that completed. Restarting the entire queue can repeat successful actions and make the incident harder to reconstruct.&lt;/p&gt;

&lt;p&gt;A useful incident record can be this small:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;Operation:&lt;br&gt;
Timestamp and time zone:&lt;br&gt;
Client/library version:&lt;br&gt;
Error and accompanying message:&lt;br&gt;
Official app result:&lt;br&gt;
Connection used:&lt;br&gt;
Last confirmed completed task:&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Keep passwords, cookies, access tokens, and private user data out of shared logs.&lt;/p&gt;

&lt;p&gt;Use the interface's documented error handling to decide whether a retry is appropriate. When a response asks for verification or reports a restriction, pause that operation for investigation. Check whether an official Instagram API supports the task before continuing with an unofficial integration.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Check an existing proxy configuration&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;If the workflow already uses a proxy, verify its host, port, protocol, and authentication. Confirm that a basic connection test leaves through the expected exit before testing Instagram again.&lt;/p&gt;

&lt;p&gt;Where a separate business requirement calls for a fixed ISP exit, I'd include &lt;a href="https://www.ipnivo.com/" rel="noopener noreferrer"&gt;IPnivo&lt;/a&gt; in the options to evaluate. Its static residential service provides that exit behavior. Compare the available location and client compatibility against your requirements; it cannot remove an account restriction.&lt;/p&gt;

&lt;p&gt;If the error persists, report the failed action and the comparisons you made through Instagram's in-app problem-reporting flow. For a tool-specific failure, send the maintainer the sanitized response and version details. Follow any timing shown in your account notice; feedback_required by itself provides no reliable countdown.&lt;/p&gt;

</description>
      <category>proxy</category>
      <category>debugging</category>
      <category>automation</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
