<?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: ProxyData</title>
    <description>The latest articles on DEV Community by ProxyData (proxydata).</description>
    <link>https://dev.to/proxydata</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%2Forganization%2Fprofile_image%2F14800%2F58b0eeb0-34fe-4c72-a170-85b879eefe34.png</url>
      <title>DEV Community: ProxyData</title>
      <link>https://dev.to/proxydata</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/proxydata"/>
    <language>en</language>
    <item>
      <title>A cheap gigabyte can cost more per usable result</title>
      <dc:creator>Alex</dc:creator>
      <pubDate>Sat, 21 Nov 2026 12:31:57 +0000</pubDate>
      <link>https://dev.to/proxydata/a-cheap-gigabyte-can-cost-more-per-usable-result-mhf</link>
      <guid>https://dev.to/proxydata/a-cheap-gigabyte-can-cost-more-per-usable-result-mhf</guid>
      <description>&lt;p&gt;Price per GB is one input to a workload budget. The useful output is the cost of a completed, validated task. The excerpts below explain what to measure, why retries matter, and how to compare two services using the same unit of useful work.&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%2Fr3obekjzq4n19jizcoig.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%2Fr3obekjzq4n19jizcoig.png" alt="Illustrative traffic purchase and the service costs it covers." width="800" height="509"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What the traffic counter measures
&lt;/h2&gt;

&lt;p&gt;A common published calculation adds &lt;strong&gt;request headers + request body + response headers + response body&lt;/strong&gt;. Both upload and download count. Cookies are part of the headers; they should not be added again if those headers are already included in a measurement.&lt;/p&gt;

&lt;p&gt;Sending 2 MB to a site and receiving 1 MB back therefore involves approximately 3 MB of application data, plus any other traffic included by the billing system. A tool reporting only downloaded response bodies will show a smaller total.&lt;/p&gt;

&lt;p&gt;The same downloaded byte passes from the website through the proxy to the customer. That does not automatically mean it is billed twice. “Upload plus download” describes the two directions of communication; the service's metering rules determine the charge.&lt;/p&gt;

&lt;p&gt;HTTPS can add handshake and encryption-related traffic to the tunnel. Some services explicitly count those bytes. Their share matters more for repeated tiny requests using new connections than for a large download. Measuring encrypted traffic volume does not require reading its contents. Keep HTTPS protection and measure the actual cost of your connection pattern.&lt;/p&gt;

&lt;p&gt;For browser work, the HTML is only part of the load. Images, scripts, stylesheets, fonts, background data calls, and media can all use the proxy. Extracting a few prices into a small CSV file may require downloading far more data than the final file contains.&lt;/p&gt;

&lt;p&gt;Compression adds another distinction: transferred bytes and the size after decompression can differ. Browser network tools show both. A locally saved, decompressed response is not a substitute for the provider's traffic counter.&lt;/p&gt;

&lt;h3&gt;
  
  
  GB, GiB, and rounding
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;1 GB is 1,000,000,000 bytes. One GiB is 1,073,741,824 bytes.&lt;/strong&gt; The same transfer has a numerical value about 7.37% larger in GB than in GiB. Commercial documentation includes an explicit change from GiB to decimal GB, so the distinction can affect real dashboard comparisons.&lt;/p&gt;

&lt;p&gt;Check the billing unit and any minimum or rounding rule. A display rounded to two decimal places does not establish that every small request is rounded up for billing. Conversely, a headline rate per GB does not promise byte-by-byte charging under every plan.&lt;/p&gt;

&lt;p&gt;GB also measures volume, not speed. A 10 GB package says nothing about how quickly it can be used. Connection limits and transfer rates remain separate service conditions.&lt;/p&gt;

&lt;h2&gt;
  
  
  Failed requests, CAPTCHAs, and paid retries
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;A request that fails your business task can still transfer billable data.&lt;/strong&gt; A CAPTCHA or access-denied page has a response body even though it contains none of the information you wanted.&lt;/p&gt;

&lt;p&gt;One published metering policy counts target-site responses such as 403, 404, and 503, plus bytes received before a transfer times out. It excludes errors generated by the proxy service itself. If the target sends nothing, the outgoing request can still count. Other products must be checked against their own rules.&lt;/p&gt;

&lt;p&gt;A retry makes another attempt and can add more traffic. Repeatedly rotating the IP and reloading the same blocked page can consume the budget while producing no usable results. Stop and diagnose a persistent failure instead of treating every error as a reason for unlimited retries.&lt;/p&gt;

&lt;p&gt;Error pages and successful pages may have different sizes, so a failure rate alone cannot tell you the wasted gigabytes. Measure the traffic from both. An HTTP 200 response also needs validation: a login screen, empty result, or challenge page may still be unusable.&lt;/p&gt;

&lt;h2&gt;
  
  
  Compare the cost of usable results
&lt;/h2&gt;

&lt;p&gt;The most useful comparison is &lt;strong&gt;total proxy spending divided by the number of usable results&lt;/strong&gt;. A cheaper gigabyte can cost more per completed task if the network requires many attempts.&lt;/p&gt;

&lt;p&gt;Here is a hypothetical comparison. Each service handles 100,000 attempts, averaging 1 MB of billed traffic per attempt, for 100 GB in total:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Service&lt;/th&gt;
&lt;th&gt;Rate&lt;/th&gt;
&lt;th&gt;Traffic cost&lt;/th&gt;
&lt;th&gt;Usable results&lt;/th&gt;
&lt;th&gt;Cost per 1,000 usable results&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;A&lt;/td&gt;
&lt;td&gt;2 USD/GB&lt;/td&gt;
&lt;td&gt;200 USD&lt;/td&gt;
&lt;td&gt;50,000&lt;/td&gt;
&lt;td&gt;4 USD&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;B&lt;/td&gt;
&lt;td&gt;3 USD/GB&lt;/td&gt;
&lt;td&gt;300 USD&lt;/td&gt;
&lt;td&gt;90,000&lt;/td&gt;
&lt;td&gt;about 3.33 USD&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Service B costs more per GB but less per useful result in this example. In your test, use measured traffic rather than assuming every success and failure is equally large. Include expired allowance or minimum commitments when they form part of the money actually spent.&lt;/p&gt;

&lt;p&gt;Scraping APIs can use another unit, such as successful requests or returned records, with the provider handling attempts internally. That cannot be compared with a raw proxy's price per GB until both are converted to the cost of the same completed task. An API's promise not to charge for failed requests does not automatically apply to that company's ordinary proxy network.&lt;/p&gt;

&lt;h2&gt;
  
  
  When unused gigabytes expire
&lt;/h2&gt;

&lt;p&gt;An allowance can expire at the end of a billing cycle, last for a specified period after purchase, or remain available without a fixed expiry. These conditions affect the amount of useful traffic the payment buys.&lt;/p&gt;

&lt;p&gt;Published arrangements include monthly GB that do not roll over, transfers of unused traffic when upgrading, and separately purchased traffic with a different expiry from the main allowance. One auto-top-up arrangement carries additional GB into the following billing cycle, then expires any remainder at the end of that cycle.&lt;/p&gt;

&lt;p&gt;“Non-expiring” also needs its account conditions read. A published residential policy says that maintaining an available balance may depend on regular top-ups or an active subscription. Check the exact rule for your account rather than assuming the wording promises access indefinitely without conditions.&lt;/p&gt;

&lt;p&gt;Suppose a 100 GB monthly package costs 200 USD. You use 20 GB and lose the remaining 80 GB at expiry. The advertised rate was 2 USD/GB, but the payment per used gigabyte was &lt;strong&gt;10 USD&lt;/strong&gt;. A smaller package with a higher unit price could have been cheaper overall.&lt;/p&gt;

&lt;p&gt;If the remaining GB stay valid and will be used later, they are not already wasted. You have paid in advance for future capacity. Also distinguish canceling the next renewal from losing access immediately: some subscriptions allow the remaining traffic to be used until the paid period ends.&lt;/p&gt;

&lt;h2&gt;
  
  
  Reduce traffic without breaking the task
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Load only what the task needs.&lt;/strong&gt; A simple HTTP request may be sufficient for a page whose required data is already in the response. A browser is appropriate when the workflow depends on rendering or interaction. Test that distinction rather than automatically loading every page in a full browser.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Stop unnecessary resources before they download.&lt;/strong&gt; Browser automation can block images, media, fonts, or selected third-party requests. Check that the changes preserve the required content and do not trigger extra reloads or failed attempts. Disabling JavaScript blindly can remove the data you came to collect.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Reuse work where freshness allows.&lt;/strong&gt; Cache reusable resources, avoid duplicate jobs, and keep suitable connections or sessions alive. Repeatedly starting a fresh browser can discard reusable state and require another full load. A sticky IP may help a session, but it does not make subsequent traffic free.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Control retries and background activity.&lt;/strong&gt; Limit attempts, pause appropriately after rate limits, and stop on persistent access or account errors. Close unused profiles and ensure system-wide proxy settings are not carrying unrelated software downloads. Keep compression enabled where supported and compare transferred sizes rather than decompressed output.&lt;/p&gt;

&lt;p&gt;Measure the result after each change: the aim is fewer paid bytes per completed task. A large reduction in downloaded data is not a saving if the task starts failing and needs to run again.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to establish before buying
&lt;/h2&gt;

&lt;p&gt;The purchase should answer five practical questions:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;What will one usable result cost?&lt;/strong&gt; Measure your workflow with the required network and filters, including errors and retries.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;What is included in the meter?&lt;/strong&gt; Confirm upload, download, overhead, units, rounding, and treatment of failures.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;How much must be paid upfront?&lt;/strong&gt; Check minimum purchases, discounts, optional features, and the price of extra GB.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;How long can the traffic be used?&lt;/strong&gt; Read expiry, rollover, cancellation, and account-activity conditions for each allowance.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;What stops further spending?&lt;/strong&gt; Confirm the behavior at zero balance, automatic purchases, sub-user limits, and any delay in enforcement.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;With those answers, the price per GB becomes a usable budget figure: you know what is counted, what the rate covers, and how much work the purchase is likely to complete.&lt;/p&gt;

&lt;p&gt;Adapted from &lt;a href="https://proxydata.io/knowledge/per-gb-pricing" rel="noopener noreferrer"&gt;ProxyData: Per GB Pricing&lt;/a&gt;. The selected technical sections reproduce the original guide; the introduction and selection were prepared with AI assistance.&lt;/p&gt;

</description>
      <category>proxy</category>
      <category>networking</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Encrypted on both links, readable in the middle</title>
      <dc:creator>Alex</dc:creator>
      <pubDate>Wed, 18 Nov 2026 12:32:06 +0000</pubDate>
      <link>https://dev.to/proxydata/encrypted-on-both-links-readable-in-the-middle-3c5n</link>
      <guid>https://dev.to/proxydata/encrypted-on-both-links-readable-in-the-middle-3c5n</guid>
      <description>&lt;p&gt;Before sending a task through a proxy service, establish where TLS ends and where readable data is processed. A normal tunnel, HTTPS inspection and a managed retrieval service expose different information. Their retention policies are a further question, not a substitute for understanding the route.&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%2Fp664ktg9na8ex8gtmz4s.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%2Fp664ktg9na8ex8gtmz4s.png" alt="Ordinary forwarding and HTTPS inspection expose different page information." width="800" height="664"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What a proxy provider can see
&lt;/h2&gt;

&lt;p&gt;Consider a request to &lt;code&gt;https://shop.example/orders/742&lt;/code&gt;. An ordinary HTTPS tunnel can reveal a connection to &lt;code&gt;shop.example:443&lt;/code&gt;, while the page path &lt;code&gt;/orders/742&lt;/code&gt;, the order details, cookies, and response stay inside the encrypted connection between your application and the website. TLS, the security protocol used by HTTPS, provides that protection.&lt;/p&gt;

&lt;p&gt;The provider can still associate the connection with your proxy account, count its bytes, and record its timing. &lt;strong&gt;An unreadable page can leave a readable connection history.&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;How the request is handled&lt;/th&gt;
&lt;th&gt;What is available to the service&lt;/th&gt;
&lt;th&gt;What stays protected from it&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Plain HTTP through a proxy&lt;/td&gt;
&lt;td&gt;Destination, page path, query parameters, HTTP headers, and request and response bodies&lt;/td&gt;
&lt;td&gt;HTTP provides no encryption for this exchange.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;HTTPS through a normal HTTP CONNECT or SOCKS5 tunnel&lt;/td&gt;
&lt;td&gt;Connection metadata; destination IP and port; the domain when disclosed during connection setup&lt;/td&gt;
&lt;td&gt;HTTP headers, page path, query parameters, and content, with correctly verified TLS and no interception&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;HTTPS inspected using a trusted interception certificate&lt;/td&gt;
&lt;td&gt;The decrypted HTTP request and response, in addition to connection metadata&lt;/td&gt;
&lt;td&gt;Only data separately encrypted above HTTPS remains unreadable to the inspecting component.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;A Scraping API or remote browser fetches the page&lt;/td&gt;
&lt;td&gt;The task you submit, the request the service makes, and the content it retrieves&lt;/td&gt;
&lt;td&gt;Information you never send to or process through that service&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The difference can exist within one provider's catalogue. Switching from its regular proxies to its managed scraping product changes how much of your work the service can inspect.&lt;/p&gt;

&lt;h2&gt;
  
  
  Provider certificates and HTTPS inspection
&lt;/h2&gt;

&lt;p&gt;An instruction to install a provider's root certificate can look like a minor setup requirement. When that certificate is used for HTTPS inspection, it changes who can read the traffic.&lt;/p&gt;

&lt;p&gt;A root certificate identifies a certificate authority, or CA, that your application agrees to trust. In an inspection setup, the intermediary uses its CA to sign certificates for the websites you visit. Your application accepts those certificates because you have granted that trust.&lt;/p&gt;

&lt;p&gt;There are then two encrypted connections. Your application sends its request to the inspecting intermediary, which decrypts it. The intermediary establishes a separate HTTPS connection to the real website, receives the response, and returns it over its connection to you. &lt;strong&gt;The traffic is encrypted on both network links, but readable where those links meet.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;This can expose full page paths, search queries, submitted form fields, authorization headers, session cookies, and downloaded pages. An ordinary tunnel cannot read your website password inside HTTPS; an inspecting component can read it if your application sends it through that connection. Data encrypted separately by the application remains a different case.&lt;/p&gt;

&lt;p&gt;This visibility has operational purposes. Managed tools use it to inspect responses, apply rules, handle blocked pages, and produce structured results. It can also support enforcement: a service able to examine requests can assess whether their contents and methods match an approved use case. Commercial network policies already describe restrictions based on approved targets and methods. &lt;strong&gt;Content visibility gives the service more control over your requests.&lt;/strong&gt; That is a material part of the product customers are agreeing to use.&lt;/p&gt;

&lt;p&gt;The scope matters. A CA trusted only by a scraping script has a narrower reach than one added to a system-wide trust store. Installation alone does not send every application through the provider, and some applications use separate certificate stores or certificate pinning. Also, an inspection tool running on your own machine does not, merely by decrypting locally, prove that the provider receives its logs.&lt;/p&gt;

&lt;p&gt;There is another certificate distinction: &lt;a href="https://proxydata.io/knowledge/http-and-https-proxies" rel="noopener noreferrer"&gt;verifying the proxy server's own HTTPS address&lt;/a&gt; is different from allowing the intermediary to issue certificates for destination websites. The former secures your connection to the proxy. The latter enables inspection when the traffic is routed through that component.&lt;/p&gt;

&lt;p&gt;Disabling certificate verification to make an error disappear gives up the check on who is answering. It does not restore privacy. For a managed product, the sensible choice is to understand the trust being requested and keep it confined to the intended workload.&lt;/p&gt;

&lt;h2&gt;
  
  
  Scraping APIs and remote browsers
&lt;/h2&gt;

&lt;p&gt;With a Scraping API, you hand the provider a task: retrieve this URL, use these options, and return HTML, JSON, or a rendered result. The provider becomes the client that visits the website. It receives the page in readable form because that is necessary to do the work.&lt;/p&gt;

&lt;p&gt;The remote browser is a browser running on the provider's server, controlled through your app or an API. It loads the website there, so pages, scripts, cookies, and sessions are processed in the provider's environment. Your connection to that browser can be encrypted while the service still has access to the task and its results.&lt;/p&gt;

&lt;p&gt;HTTPS inspection, a Scraping API, and a provider-hosted browser all give the provider access to page content, but by different routes. Inspection ends your HTTPS connection at the intermediary. The managed tools make their own connection to the site after you submit a task. A Scraping API can therefore have this visibility without asking you to install a provider certificate.&lt;/p&gt;

&lt;p&gt;This access is part of the work these products perform. An API cannot return a page or extracted data without receiving the website response; a hosted browser must process the page to display it. Technical access does not establish that employees routinely inspect customer tasks, that every page is saved, or that data is shared with others. Processing, persistent logs, and staff access are separate questions; managed products may also have retention terms different from ordinary proxy traffic.&lt;/p&gt;

&lt;p&gt;Depending on the product, the information supplied can include full URLs, search terms, custom headers, cookies, POST bodies, location settings, and instructions for interacting with a page. Anything the tool does not support cannot be assumed to be accepted. But the items you do supply should be treated as information entrusted to that service.&lt;/p&gt;

&lt;p&gt;For a business, the sensitive material may be its list of monitored products, a sequence of searches, or access tokens for a permitted task. None needs to be a password to have commercial value. &lt;strong&gt;Outsourcing page retrieval also gives the service visibility into that part of your workflow.&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Retention, deletion, and backups
&lt;/h2&gt;

&lt;p&gt;There is no single retention clock for an entire proxy service. Connection history, invoices, verification records, support cases, and scraped results can each have different lifetimes.&lt;/p&gt;

&lt;p&gt;For a concrete published example, one provider sets connection-metadata retention at the active billing period plus up to 90 days, billing records at seven years, and account records at the subscription lifetime plus two years, subject to its stated deletion conditions. These are that provider's periods, not industry-wide defaults.&lt;/p&gt;

&lt;p&gt;Customer-visible history is another matter. A dashboard or export API showing the last 30 or 90 days describes what you can retrieve there. It does not, by itself, establish when all internal copies are destroyed. Samples retained in support tickets or abuse cases may follow separate rules.&lt;/p&gt;

&lt;p&gt;Closing an account also does not automatically erase every associated record. Where GDPR or similar rights apply, deletion requests must be assessed alongside exceptions such as legal obligations and the establishment or defence of legal claims. Records needed for those purposes can outlast the account.&lt;/p&gt;

&lt;p&gt;Backup removal may follow a different schedule from deletion in a live system. Relevant privacy guidance allows for backup handling that puts deleted information beyond use until the backup is overwritten. “Deleted from the dashboard” and “removed from every retained copy” are different events.&lt;/p&gt;

&lt;p&gt;Encryption at rest protects stored data against certain forms of unauthorized access. Replacing a name with an account number can reduce exposure. Neither makes records anonymous if the operator retains the means to connect them with a customer.&lt;/p&gt;

&lt;h2&gt;
  
  
  Business confidentiality and practical choices
&lt;/h2&gt;

&lt;p&gt;Even destination metadata can be commercially sensitive. A collection of target domains, its timing, and the scale of access can reveal which market a team monitors or suggest an upcoming project. Full scraping instructions and results can expose considerably more.&lt;/p&gt;

&lt;p&gt;For an ordinary HTTPS workload, a properly verified tunnel keeps the page contents between the application and the website. Choosing an inspected connection, remote browser, or managed API means entrusting that service with the data needed to perform the task. That can be a reasonable business decision when its access, retention, and contractual terms fit the project.&lt;/p&gt;

&lt;p&gt;Credentials deserve particular care. Request logging should avoid or mask passwords, authorization tokens, and session secrets where possible. A customer can also reveal them voluntarily by sending a configuration file, screenshot, or browser network capture to support. Even a sanitized HAR export should be checked for sensitive URLs and bodies before it is shared.&lt;/p&gt;

&lt;p&gt;Labels such as &lt;strong&gt;elite&lt;/strong&gt;, &lt;strong&gt;private&lt;/strong&gt;, &lt;strong&gt;dedicated&lt;/strong&gt;, and &lt;strong&gt;residential&lt;/strong&gt; do not define a logging policy. A public anonymity checker sees the request that arrives at its own website; it cannot inspect the proxy operator's internal records. Cryptocurrency payment and the absence of a passport check do not remove connection history either. Running a proxy on your own VPS gives you control over that proxy process, while hosting, billing, and destination-site records remain separate.&lt;/p&gt;

&lt;p&gt;The most useful privacy promise explains five things: &lt;strong&gt;what the service can access, what it records, how long it keeps it, who can use it, and when it may disclose it&lt;/strong&gt;. Those details tell a customer far more than an unqualified no-logs badge. HTTPS protects content within a particular connection; the architecture of the proxy product determines who stands at its ends.&lt;/p&gt;

&lt;p&gt;Adapted from &lt;a href="https://proxydata.io/knowledge/proxy-logging" rel="noopener noreferrer"&gt;ProxyData: Proxy Logging and Privacy&lt;/a&gt;. The selected technical sections reproduce the original guide; the introduction and selection were prepared with AI assistance.&lt;/p&gt;

</description>
      <category>proxy</category>
      <category>networking</category>
      <category>webdev</category>
    </item>
    <item>
      <title>An ISP address does not prove a household route</title>
      <dc:creator>Alex</dc:creator>
      <pubDate>Mon, 16 Nov 2026 12:31:58 +0000</pubDate>
      <link>https://dev.to/proxydata/an-isp-address-does-not-prove-a-household-route-5b60</link>
      <guid>https://dev.to/proxydata/an-isp-address-does-not-prove-a-household-route-5b60</guid>
      <description>&lt;h1&gt;
  
  
  An ISP address does not prove a household route
&lt;/h1&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%2Fao6cyzhked9rqrj9g754.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%2Fao6cyzhked9rqrj9g754.png" alt="ISP Proxies" width="800" height="420"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;An ISP proxy can use a broadband provider's address while running on a server in a datacenter. The network associated with an IP and the equipment forwarding the traffic are different facts.&lt;/p&gt;

&lt;h2&gt;
  
  
  Address classification and physical equipment
&lt;/h2&gt;

&lt;p&gt;Your application connects to the proxy endpoint. The service then opens a connection to the destination using its ISP-associated exit address. That path does not have to pass through a subscriber's home router.&lt;/p&gt;

&lt;p&gt;This is why the label “static residential” needs interpretation. It often describes server-hosted ISP addresses that can remain assigned over time. It does not, on its own, establish household-device participation, exclusive access or an unchanging exit.&lt;/p&gt;

&lt;h2&gt;
  
  
  Four questions for a repeatable test
&lt;/h2&gt;

&lt;p&gt;Before choosing a service, separate these questions:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Which exit address does the destination actually see?&lt;/li&gt;
&lt;li&gt;How long is that address assigned to the workload?&lt;/li&gt;
&lt;li&gt;Can another customer use the same address during that period?&lt;/li&gt;
&lt;li&gt;Does the task need an ISP classification, or does it specifically require traffic through a household connection?&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;A fixed address can be shared. A dedicated address can use shared hardware. A sticky session can retain a pool exit temporarily without reserving it for the whole subscription.&lt;/p&gt;

&lt;h2&gt;
  
  
  Test the destination, not just the label
&lt;/h2&gt;

&lt;p&gt;An IP database's classification does not settle how the target will respond. The target can use another database and can also evaluate request patterns, cookies and account activity.&lt;/p&gt;

&lt;p&gt;For a recurring regional check, run the same sequence of pages with the browser state and session duration the real job requires. Record whether the expected content loads and whether the exit remains stable through the sequence.&lt;/p&gt;

&lt;p&gt;ISP proxies can be useful when the task benefits from ISP-associated addresses and managed server availability. Their value comes from those observed properties, rather than an assumption about a house somewhere along the route.&lt;/p&gt;

&lt;p&gt;Source: &lt;a href="https://proxydata.io/knowledge/isp-proxies" rel="noopener noreferrer"&gt;ProxyData — ISP Proxies&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;This adaptation was prepared with AI assistance.&lt;/p&gt;

</description>
      <category>proxy</category>
      <category>networking</category>
      <category>webdev</category>
    </item>
    <item>
      <title>A working SOCKS5 proxy does not prove UDP support</title>
      <dc:creator>Alex</dc:creator>
      <pubDate>Sat, 14 Nov 2026 17:08:51 +0000</pubDate>
      <link>https://dev.to/proxydata/a-working-socks5-proxy-does-not-prove-udp-support-2apl</link>
      <guid>https://dev.to/proxydata/a-working-socks5-proxy-does-not-prove-udp-support-2apl</guid>
      <description>&lt;p&gt;A proxy test that only opens an HTTPS page cannot establish UDP support. The application may use TCP, fall back from HTTP/3, or apply its proxy setting to only part of its traffic. Diagnose the client, relay and destination as separate parts of the path.&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%2Flkyq2hw06gmjtckyqeui.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%2Flkyq2hw06gmjtckyqeui.png" alt="SOCKS5 control connection and separate UDP relay path." width="800" height="509"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  UDP, QUIC and HTTP/3 have different jobs
&lt;/h2&gt;

&lt;p&gt;TCP supplies an ordered stream of bytes and handles retransmission when data is lost. UDP sends separate messages, called datagrams, without providing those delivery and ordering guarantees itself. Software using UDP decides how to deal with missing, late or duplicate messages.&lt;/p&gt;

&lt;p&gt;That makes UDP useful for applications with different priorities. A live voice application may prefer the next audio packet to a delayed replacement of an old one. A game can send frequent state updates. DNS can use a short request and response. These examples do not mean that every call, game or DNS lookup always uses UDP; the actual application can have several transports and fallback modes.&lt;/p&gt;

&lt;p&gt;QUIC runs over UDP and adds its own connection management, loss recovery, congestion control and secure communication. Its reliable streams can carry a complete webpage or file. &lt;strong&gt;Using UDP does not make QUIC an unreliable file-transfer protocol.&lt;/strong&gt; Reliability is supplied at a different level.&lt;/p&gt;

&lt;p&gt;HTTP/3 is HTTP carried over QUIC. HTTP/1.1 and HTTP/2 ordinarily use TCP. An HTTPS address can therefore be reached using different transports; the &lt;code&gt;https://&lt;/code&gt; prefix alone does not tell you which one was used. Supporting HTTPS websites and supporting HTTP/3 are separate claims.&lt;/p&gt;

&lt;p&gt;UDP itself also provides no encryption. QUIC protects application data using TLS 1.3, while another protocol using UDP may have different protection or none. Forwarding a datagram and protecting its contents are separate functions.&lt;/p&gt;

&lt;h2&gt;
  
  
  How SOCKS5 forwards UDP
&lt;/h2&gt;

&lt;p&gt;SOCKS5 uses a TCP connection to arrange UDP forwarding. That TCP connection stays open, but the UDP payload travels separately. The arrangement works as follows:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Open the control connection.&lt;/strong&gt; The client reaches the SOCKS5 endpoint over TCP and completes any required authentication.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Request a UDP relay.&lt;/strong&gt; It sends &lt;code&gt;UDP ASSOCIATE&lt;/code&gt;. The proxy replies with the relay address and UDP port the client should use.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Send datagrams to the relay.&lt;/strong&gt; The client adds a SOCKS header containing the destination address and port. The relay forwards the payload and returns replies with the corresponding SOCKS framing.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Keep the control connection open.&lt;/strong&gt; Closing it ends the UDP association, even if the application still wants to send datagrams.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The returned relay endpoint is not necessarily the proxy's TCP listening endpoint. Sending raw UDP to the usual SOCKS port is not a substitute for this exchange. A client that only implements SOCKS &lt;code&gt;CONNECT&lt;/code&gt; can establish TCP connections but cannot perform this UDP forwarding procedure.&lt;/p&gt;

&lt;p&gt;Consider a company network that permits TCP to the proxy but blocks the separate UDP relay path. Authentication can succeed while no application datagrams get through. Replacing a correct password or selecting another website will not address that restriction; the missing part is access to the relay path.&lt;/p&gt;

&lt;p&gt;Remote DNS for a SOCKS TCP connection is a different operation. Passing a hostname to the proxy for resolution does not exercise the application's UDP relay. A successful hostname lookup cannot replace a UDP test.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;TCP setup can succeed even when the separate UDP path to the negotiated relay is blocked.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  UDP forwarding through HTTP proxies
&lt;/h2&gt;

&lt;p&gt;An ordinary HTTP &lt;code&gt;CONNECT&lt;/code&gt; tunnel carries a byte stream to a TCP destination. &lt;strong&gt;It does not provide UDP forwarding.&lt;/strong&gt; Encrypting the connection to the proxy does not change that, and specifying destination port &lt;code&gt;443&lt;/code&gt; does not turn a TCP tunnel into a UDP tunnel.&lt;/p&gt;

&lt;p&gt;HTTP can carry UDP when both sides implement a separate UDP tunneling facility, commonly called &lt;strong&gt;CONNECT-UDP&lt;/strong&gt;, from the MASQUE family of mechanisms. The client identifies a UDP destination, establishes the tunnel and exchanges datagrams through it. The proxy sends those payloads onward over UDP and carries replies back. This is an additional capability, not something every HTTP or HTTPS proxy already provides.&lt;/p&gt;

&lt;p&gt;The transport used between the client and the proxy matters too. HTTP/3 can carry HTTP Datagrams in QUIC DATAGRAM frames. The Capsule Protocol also allows datagrams to be carried in a reliable stream, including with HTTP/2 over TCP. A service and a compatible client must agree on the supported method.&lt;/p&gt;

&lt;p&gt;The reliable-stream option preserves the messages, but it changes how delays behave. On a TCP segment of the route, later data can wait for a missing segment to be recovered. That can matter to time-sensitive applications even when UDP forwarding is functionally working. A tunnel that works on a restrictive network and a tunnel that gives the best timing for voice or a game are not necessarily the same choice.&lt;/p&gt;

&lt;p&gt;Entering an ordinary &lt;code&gt;http://&lt;/code&gt; proxy address into a program does not enable these extensions. The program needs an actual UDP tunneling implementation and the service's corresponding configuration. A provider offering only standard CONNECT cannot meet that requirement by changing the endpoint's label.&lt;/p&gt;

&lt;h2&gt;
  
  
  Which connection uses QUIC?
&lt;/h2&gt;

&lt;p&gt;A claim such as “QUIC proxy” needs a clear description of the connection it refers to. There are two distinct possibilities:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The connection to the proxy uses QUIC.&lt;/strong&gt; This describes how the client reaches the proxy. For example, ordinary CONNECT over HTTP/3 still asks the proxy to open a TCP connection to the destination. QUIC on the first part of the route does not establish HTTP/3 with the website.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The application uses QUIC with the destination through a UDP relay.&lt;/strong&gt; Here, the relay carries the application's QUIC packets onward. The application's HTTP/3 connection can reach the website through SOCKS5 UDP forwarding or an appropriate HTTP UDP tunnel, provided the client actually uses that mechanism and the path meets its requirements.&lt;/p&gt;

&lt;p&gt;The distinction is especially relevant to testing. A browser or network log showing QUIC traffic to a proxy proves something about that connection. It does not, by itself, prove that the target website was reached using HTTP/3.&lt;/p&gt;

&lt;p&gt;In ordinary UDP relaying, the proxy does not need to terminate the application's QUIC connection to forward its datagrams. The application and destination remain the endpoints of that exchange. The proxy still handles destination addresses and traffic, so encrypted content should not be confused with an invisible route.&lt;/p&gt;

&lt;h2&gt;
  
  
  Fallback, failure and traffic outside the proxy
&lt;/h2&gt;

&lt;p&gt;When the requested transport is unavailable, software can behave in different ways. These outcomes should be distinguished when reading a test result:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Observed outcome&lt;/th&gt;
&lt;th&gt;What happened&lt;/th&gt;
&lt;th&gt;What it means for the test&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;The operation fails&lt;/td&gt;
&lt;td&gt;The required exchange did not complete&lt;/td&gt;
&lt;td&gt;Identify whether the failure occurred at the client, relay, network or destination.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;The website works using HTTP/2 or HTTP/1.1&lt;/td&gt;
&lt;td&gt;The client used a TCP-based HTTP connection instead of HTTP/3&lt;/td&gt;
&lt;td&gt;Web access works, but this result does not demonstrate QUIC forwarding.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;UDP goes directly to the destination&lt;/td&gt;
&lt;td&gt;The traffic bypassed the intended proxy&lt;/td&gt;
&lt;td&gt;The destination receives traffic from the direct route, not the proxy route you wanted to test.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;HTTP clients can try a TCP-based version when an HTTP/3 connection cannot be established. This can be useful for ordinary browsing. It is misleading only when page loading is treated as proof that a required HTTP/3 path worked. QUIC did not turn into TCP; the client used a different connection and HTTP version.&lt;/p&gt;

&lt;p&gt;Direct traffic is a different issue from a transport fallback. It depends on the application's routing and bypass policy, not on a rule that unsupported UDP must always be sent directly. If using the proxy is mandatory, configure the client or routing layer to stop when that path is unavailable. A successful operation after deliberately disabling the proxy is a reason to inspect the route.&lt;/p&gt;

&lt;p&gt;Disabling QUIC can be a valid way to keep ordinary web traffic on a supported TCP path. It does not add UDP capability and does not solve an application that actually requires UDP. Decide whether the task needs the result, such as a webpage, or specifically needs that transport, such as an HTTP/3 test.&lt;/p&gt;

&lt;h2&gt;
  
  
  Verify the transport and the exit address
&lt;/h2&gt;

&lt;p&gt;A useful test establishes both &lt;strong&gt;what was sent&lt;/strong&gt; and &lt;strong&gt;which route carried it&lt;/strong&gt;. Use the application you intend to run, or a test client that explicitly supports the same forwarding method. A generic proxy check in another tool may exercise a different feature.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Choose a destination that answers the required traffic.&lt;/strong&gt; For UDP, use a controlled test service or the actual application server. Include an identifier in a test request so its reply can be matched. For HTTP/3, use a target known to serve HTTP/3 on the intended port. Silence from an arbitrary UDP port does not diagnose the proxy.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Confirm that forwarding was established.&lt;/strong&gt; For SOCKS5, inspect the result of &lt;code&gt;UDP ASSOCIATE&lt;/code&gt; and the returned relay endpoint. For an HTTP UDP tunnel, confirm that the requested tunnel was accepted. A login success or an open TCP socket is not this evidence.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Observe a complete exchange.&lt;/strong&gt; Confirm that the expected reply arrives through the configured client. A destination log or a controlled responder can record the source address it saw. This establishes the exit used for that UDP exchange; an IP-check page opened separately establishes only the route of its own request.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;For HTTP/3, verify the actual protocol.&lt;/strong&gt; Inspect the application's protocol log or the destination's connection log. Look for HTTP/3 (&lt;code&gt;h3&lt;/code&gt;) for the destination exchange, not merely QUIC on the connection to the proxy. Where the test client offers an HTTP/3-only mode, use it to prevent a TCP fallback from concealing failure. Combine protocol confirmation with evidence of the intended proxy route.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Exercise the conditions that matter.&lt;/strong&gt; Repeat with representative packet sizes, traffic duration and idle periods. If bypass must be prevented, test the client's behavior when the configured proxy is unavailable. Record the endpoint, client version and settings so the result can be reproduced.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;A packet capture on your device can help locate a failure. In a standard SOCKS5 UDP exchange, it should show datagrams going to the negotiated relay rather than directly to the target. With an HTTP UDP tunnel, the outer connection may instead be HTTP/3 or a reliable HTTP stream. The absence of visible UDP packets on the first leg does not disprove UDP forwarding through that latter method.&lt;/p&gt;

&lt;p&gt;Do not treat remote DNS or &lt;code&gt;ping&lt;/code&gt; as replacements for these checks. A name can be resolved by the proxy without relaying the application's UDP, and ordinary ping uses ICMP. Neither demonstrates the complete UDP request-and-reply path your application needs.&lt;/p&gt;

&lt;p&gt;Adapted from &lt;a href="https://proxydata.io/knowledge/udp-quic-support-in-proxies" rel="noopener noreferrer"&gt;ProxyData: UDP and QUIC Support in Proxies&lt;/a&gt;. The selected technical sections reproduce the original guide; the introduction and selection were prepared with AI assistance.&lt;/p&gt;

</description>
      <category>proxy</category>
      <category>networking</category>
      <category>webdev</category>
    </item>
    <item>
      <title>More proxy IPs are not more server capacity</title>
      <dc:creator>Alex</dc:creator>
      <pubDate>Mon, 09 Nov 2026 12:41:58 +0000</pubDate>
      <link>https://dev.to/proxydata/more-proxy-ips-are-not-more-server-capacity-1n0m</link>
      <guid>https://dev.to/proxydata/more-proxy-ips-are-not-more-server-capacity-1n0m</guid>
      <description>&lt;h1&gt;
  
  
  More proxy IPs are not more server capacity
&lt;/h1&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%2F10v2mdfrg02f85pdbm2d.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%2F10v2mdfrg02f85pdbm2d.png" alt="Datacenter Proxies" width="800" height="420"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;A datacenter proxy list counts addresses. It does not count physical servers, reserved bandwidth or simultaneous connections. This distinction matters when a larger package fails to make a collection job finish faster.&lt;/p&gt;

&lt;h2&gt;
  
  
  Separate the resources
&lt;/h2&gt;

&lt;p&gt;One server can use multiple public IP addresses. Its proxy software chooses an available source address for an outgoing connection. Several customers may use the same hardware while receiving different addresses.&lt;/p&gt;

&lt;p&gt;A dedicated IP allocation reserves those addresses for you. It does not automatically reserve the machine or its network link. Similarly, rotating to another exit does not prove that traffic moved to a different server.&lt;/p&gt;

&lt;p&gt;Suppose a hypothetical workload has enough addresses but repeatedly reaches its connection allowance. Adding addresses without increasing that allowance leaves the limit unchanged. If the bottleneck is bandwidth, a larger list can still share the same constrained link.&lt;/p&gt;

&lt;h2&gt;
  
  
  Measure the job you need to complete
&lt;/h2&gt;

&lt;p&gt;Record three things during a representative run:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;How many requested pages produce usable content.&lt;/li&gt;
&lt;li&gt;How long the job takes at the intended number of concurrent connections.&lt;/li&gt;
&lt;li&gt;Which resource limit or failure appears as load increases.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A fast challenge page is not a successful collection result. A response from an IP-check page establishes basic connectivity, but does not establish access to the intended destination.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check network variety separately
&lt;/h2&gt;

&lt;p&gt;Several addresses can belong to the same range or ASN. If a destination restricts that network, switching between those addresses may not change the response. Address count and network variety answer different questions.&lt;/p&gt;

&lt;p&gt;The purchasing decision follows the observed constraint. A small fixed list may be enough for a stable outbound address. A larger allocation may help when distinct addresses are actually required. More throughput needs suitable server capacity, connectivity and plan limits.&lt;/p&gt;

&lt;p&gt;Source: &lt;a href="https://proxydata.io/knowledge/datacenter-proxies" rel="noopener noreferrer"&gt;ProxyData — Datacenter Proxies&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;This adaptation was prepared with AI assistance.&lt;/p&gt;

</description>
      <category>proxy</category>
      <category>networking</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Count proxy connections across the account, not just workers</title>
      <dc:creator>Alex</dc:creator>
      <pubDate>Sat, 07 Nov 2026 12:32:01 +0000</pubDate>
      <link>https://dev.to/proxydata/count-proxy-connections-across-the-account-not-just-workers-2ac6</link>
      <guid>https://dev.to/proxydata/count-proxy-connections-across-the-account-not-just-workers-2ac6</guid>
      <description>&lt;p&gt;A proxy limit of twelve concurrent connections can be exhausted by three small clients. No single client needs twelve workers to reach it.&lt;/p&gt;

&lt;p&gt;Consider this illustrative snapshot:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Client&lt;/th&gt;
&lt;th&gt;Open connections counted against the shared limit&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Browser profile A&lt;/td&gt;
&lt;td&gt;6&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Browser profile B&lt;/td&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;HTTP client&lt;/td&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Total&lt;/td&gt;
&lt;td&gt;12&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;All twelve slots are occupied. In a product that rejects new connections at this limit, the next connection fails while existing connections remain active. These are example counts, not a measurement of a provider or a universal rule for how overload is handled.&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%2Ft7y4suf6waedyx7ai87q.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%2Ft7y4suf6waedyx7ai87q.png" alt="Three clients share a twelve-connection allowance." width="800" height="539"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Find the scope of the limit
&lt;/h2&gt;

&lt;p&gt;Before changing code, establish whether the allowance applies to the account, product, credential set, IP or another resource. Two applications can share a limit even when they run on different machines. Giving each application its own local cap does not keep their combined total below the account cap.&lt;/p&gt;

&lt;p&gt;Confirm what is counted, too. A request, a worker and an open connection are different units. A browser can open several connections while loading a page. A client can retain an idle connection for reuse. Protocol multiplexing can carry more than one request on a connection. The mapping depends on the client, protocol and service.&lt;/p&gt;

&lt;h2&gt;
  
  
  Measure before raising the worker count
&lt;/h2&gt;

&lt;p&gt;Record active and idle connections, request duration, attempts and successful results. Check whether another process uses the same allowance. A rise in retries can add work precisely when the system has little spare capacity.&lt;/p&gt;

&lt;p&gt;Average in-flight requests can be estimated as request rate multiplied by average request duration in a stable workload. For example, five requests per second taking two seconds on average imply about ten requests in flight. That estimate becomes a connection estimate only if the workload really uses one counted connection for each in-flight request. It also says little about short bursts.&lt;/p&gt;

&lt;h2&gt;
  
  
  Keep the combined load bounded
&lt;/h2&gt;

&lt;p&gt;Use a shared concurrency budget across the clients that consume the same quota, or allocate explicit portions of that budget to them. Leave headroom for browser traffic and operational checks. Release unused connections according to the client's documented behaviour.&lt;/p&gt;

&lt;p&gt;If the service reports overload, use bounded retries with backoff and a stop condition. Unbounded retries can keep the account saturated. Distinguish a provider connection limit from a target website's rate limit before choosing a response.&lt;/p&gt;

&lt;p&gt;A higher allowance can be appropriate once measurement shows that useful work needs it. Increasing workers alone does not show that the bottleneck has moved.&lt;/p&gt;

&lt;p&gt;Source: &lt;a href="https://proxydata.io/knowledge/limited-concurrent-connections" rel="noopener noreferrer"&gt;ProxyData: Limited Concurrent Connections&lt;/a&gt;. This adaptation was prepared with AI assistance.&lt;/p&gt;

</description>
      <category>proxy</category>
      <category>networking</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Why a registry country change may leave a website in the wrong country</title>
      <dc:creator>Alex</dc:creator>
      <pubDate>Wed, 04 Nov 2026 12:31:58 +0000</pubDate>
      <link>https://dev.to/proxydata/why-a-registry-country-change-may-leave-a-website-in-the-wrong-country-2oma</link>
      <guid>https://dev.to/proxydata/why-a-registry-country-change-may-leave-a-website-in-the-wrong-country-2oma</guid>
      <description>&lt;p&gt;A proxy is sold with a Japan location. A registry lookup also shows Japan. The target website still places the request in the United States. Those observations can coexist because they may come from different records.&lt;/p&gt;

&lt;h2&gt;
  
  
  Follow one address through the records
&lt;/h2&gt;

&lt;p&gt;Consider a fictional example using the documentation address 198.51.100.42. A provider leases an address range and selects part of it for a Japan-labelled service. The relevant registry record is updated to Japan. A GeoIP database still has an older United States assignment for the same address.&lt;/p&gt;

&lt;p&gt;For this example, assume the target website uses that GeoIP database. The website returns United States because that is the record it consults. The registry change did not automatically replace the website's location data.&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%2Fh5hih6qdynk825h5d49g.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%2Fh5hih6qdynk825h5d49g.png" alt="The same documentation IP has different illustrative registry and GeoIP country records." width="800" height="749"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;These are illustrative records, not a live lookup or proof of a server's physical location. A registry field, an advertised product location, a database classification and a website's behaviour answer different questions.&lt;/p&gt;

&lt;h2&gt;
  
  
  Make the comparison reproducible
&lt;/h2&gt;

&lt;p&gt;First, record the actual exit IP used by the application. If the proxy rotates between checks, two apparently conflicting results may concern different addresses. Keep the exit stable where the product supports it and record the time of each test.&lt;/p&gt;

&lt;p&gt;Next, compare named GeoIP data sources. Several checker websites can consult the same underlying supplier. Agreement between three checker pages is weaker evidence than it appears if all three read the same data. Record the database and version or update date when they are available.&lt;/p&gt;

&lt;p&gt;Then examine what the target actually does. An IP-country result is different from a stored country selector, account region, delivery address or browser location permission. A website may combine several signals. Do not infer its database supplier from one result alone.&lt;/p&gt;

&lt;h2&gt;
  
  
  Choose the repair that matches the evidence
&lt;/h2&gt;

&lt;p&gt;If a location record is wrong, the provider or range holder may be able to submit a correction to the relevant database. Correction review, database publication and the target's adoption of an update are separate steps. None guarantees immediate change on every website.&lt;/p&gt;

&lt;p&gt;If the target continues to classify that exit incorrectly for the task, ask whether a replacement exit can be checked against the same target. Repeating a registry lookup does not establish that the website's behaviour changed.&lt;/p&gt;

&lt;p&gt;Changing to a different proxy network type is not, by itself, proof that the mismatch will disappear. Validate the actual address and the actual target with the same test conditions.&lt;/p&gt;

&lt;p&gt;Source: &lt;a href="https://proxydata.io/knowledge/proxy-geolocation-mismatch" rel="noopener noreferrer"&gt;ProxyData: Proxy Geolocation Mismatch&lt;/a&gt;. This adaptation was prepared with AI assistance.&lt;/p&gt;

</description>
      <category>proxy</category>
      <category>networking</category>
      <category>webdev</category>
    </item>
    <item>
      <title>The proxy worked at home. Why does it fail on a VPS?</title>
      <dc:creator>Alex</dc:creator>
      <pubDate>Sat, 31 Oct 2026 12:37:02 +0000</pubDate>
      <link>https://dev.to/proxydata/the-proxy-worked-at-home-why-does-it-fail-on-a-vps-4m4l</link>
      <guid>https://dev.to/proxydata/the-proxy-worked-at-home-why-does-it-fail-on-a-vps-4m4l</guid>
      <description>&lt;p&gt;You move a working application from your laptop to a VPS. The proxy hostname, port and code stay the same, but access stops working. If the endpoint uses IP authentication, check the address arriving at the proxy before changing the application.&lt;/p&gt;

&lt;h2&gt;
  
  
  The allowlist checks the incoming connection
&lt;/h2&gt;

&lt;p&gt;The provider compares your connection's public source IP with an allowed list. This is the address of the machine or network reaching the proxy. The proxy's exit IP is a different address, used when it connects onward to the destination.&lt;/p&gt;

&lt;p&gt;Consider an illustrative setup using documentation addresses:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Client&lt;/th&gt;
&lt;th&gt;Public source IP&lt;/th&gt;
&lt;th&gt;On the allowlist?&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Home computer&lt;/td&gt;
&lt;td&gt;198.51.100.24&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;VPS&lt;/td&gt;
&lt;td&gt;203.0.113.17&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The home request is accepted. The VPS request fails the source-IP check. Adding the proxy's exit IP would not correct this mismatch.&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%2Fi7fineclz69kwiqk5i9b.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%2Fi7fineclz69kwiqk5i9b.png" alt="A home connection is allowed; a VPS connection has a different public source IP." width="800" height="479"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Check the route used by the application
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Confirm that the purchased endpoint is configured for IP authentication. Some products use a different endpoint or port for username/password access.&lt;/li&gt;
&lt;li&gt;Determine the public outbound address from the machine running the application, on the route used to reach the proxy. A lookup from your laptop cannot tell you the VPS address.&lt;/li&gt;
&lt;li&gt;Account for a NAT gateway, VPN, container host or other outbound gateway. The local interface address may be private, and a VPN may change the public source.&lt;/li&gt;
&lt;li&gt;Check the address family. An IPv4 allowlist entry does not authorize a separate IPv6 source address. Use the provider's supported method for the family involved.&lt;/li&gt;
&lt;li&gt;Compare the observed source with the provider's allowed entries. Update the relevant entry if authorized, allow for the provider's documented propagation time, and retry with a fresh connection.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;An IP-checking request sent &lt;em&gt;through&lt;/em&gt; the proxy normally reports the proxy exit. That is useful for checking the destination-facing address, but it does not identify the address the proxy saw on the incoming connection. Direct checks can also be misleading with destination-dependent routing. Provider connection logs or a controlled test on the actual route can help resolve that case.&lt;/p&gt;

&lt;h2&gt;
  
  
  Decide whether the address is stable enough
&lt;/h2&gt;

&lt;p&gt;A home connection can receive a different public address after a reconnect. Cloud workloads may also share or change outbound gateways. Automatic allowlist updates are useful only if the provider supports them and the update process is reliable.&lt;/p&gt;

&lt;p&gt;For frequently changing sources, username/password authentication may be easier to operate when the product supports it. That choice does not make the transport encrypted: protect the connection to the proxy separately.&lt;/p&gt;

&lt;p&gt;Once the source-IP check passes, investigate later stages separately. A destination-side login page or access denial is not evidence that the proxy allowlist failed.&lt;/p&gt;

&lt;p&gt;Source: &lt;a href="https://proxydata.io/knowledge/ip-authentication" rel="noopener noreferrer"&gt;ProxyData: IP Authentication&lt;/a&gt;. This adaptation was prepared with AI assistance.&lt;/p&gt;

</description>
      <category>proxy</category>
      <category>networking</category>
      <category>webdev</category>
    </item>
    <item>
      <title>HTTP proxy or HTTPS proxy? Check which connection uses TLS</title>
      <dc:creator>Alex</dc:creator>
      <pubDate>Sat, 10 Oct 2026 12:31:57 +0000</pubDate>
      <link>https://dev.to/proxydata/http-proxy-or-https-proxy-check-which-connection-uses-tls-16ol</link>
      <guid>https://dev.to/proxydata/http-proxy-or-https-proxy-check-which-connection-uses-tls-16ol</guid>
      <description>&lt;p&gt;An HTTPS page can load successfully while your proxy login travels without TLS protection. The website connection and the connection to the proxy have separate security properties.&lt;/p&gt;

&lt;p&gt;This distinction matters when you configure a client, read a provider's “HTTPS supported” label, or investigate a TLS error. Start with two questions: does the destination use HTTPS, and does the proxy endpoint itself accept TLS?&lt;/p&gt;

&lt;h2&gt;
  
  
  How HTTP and HTTPS traffic passes through a proxy
&lt;/h2&gt;

&lt;p&gt;For an ordinary HTTP website, your application sends the request to the proxy. The proxy contacts the website, retrieves the response and sends it back. It handles the request as HTTP, so it can read the requested page address, headers and any content sent with the request.&lt;/p&gt;

&lt;p&gt;For an HTTPS website, the application first asks the proxy to open a connection to the destination, such as &lt;code&gt;example.com:443&lt;/code&gt;. This request uses the HTTP method &lt;strong&gt;CONNECT&lt;/strong&gt;. After the proxy accepts it, the application establishes TLS with the website through the resulting tunnel. TLS is the encryption used by HTTPS.&lt;/p&gt;

&lt;p&gt;The proxy forwards the encrypted traffic in both directions. It does not need to decrypt the page to deliver it. The application checks the website's certificate, just as it would when connecting directly. CONNECT creates the tunnel; TLS protects the data sent through it.&lt;/p&gt;

&lt;p&gt;HTTP describes the connection protocol, not the source or allocation of the IP address. HTTP access can be offered with datacenter, ISP, residential or mobile addresses, and with fixed or rotating exits.&lt;/p&gt;

&lt;h2&gt;
  
  
  HTTPS websites and HTTPS proxy connections
&lt;/h2&gt;

&lt;p&gt;There are two different capabilities to distinguish when reading a proxy description or choosing a setting.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;HTTPS website support&lt;/strong&gt; means that the proxy can carry a connection to an HTTPS destination. An ordinary HTTP proxy can do this using CONNECT. Your application's conversation with the website is encrypted, but the initial request to the proxy is not.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;An HTTPS proxy connection&lt;/strong&gt; means that your application establishes TLS with the proxy itself. Requests to the proxy, including CONNECT and proxy authentication, travel inside that protected connection. When the destination is also HTTPS, its own TLS connection runs through the tunnel. The proxy removes the outer layer of encryption; the website's traffic inside remains encrypted.&lt;/p&gt;

&lt;p&gt;These capabilities are not interchangeable. A service that lets you open HTTPS websites does not necessarily accept TLS connections on its proxy port. To use an HTTPS proxy connection, both the proxy endpoint and your application must support it.&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%2Fm8xbm05cnn5hpe4f3rdu.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%2Fm8xbm05cnn5hpe4f3rdu.png" alt="An HTTP proxy and an HTTPS proxy both forward encrypted HTTPS website data. The HTTPS proxy adds a separate TLS layer from the app to the proxy, protecting CONNECT and Basic proxy authentication on that connection." width="800" height="629"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;HTTPS protects the website content in both cases. TLS to an HTTPS proxy additionally protects the connection to the proxy, including CONNECT and Basic proxy authentication. Ordinary CONNECT forwarding with valid certificate checks is shown; HTTPS interception is excluded.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What the proxy can see
&lt;/h2&gt;

&lt;p&gt;The following comparison assumes normal forwarding without HTTPS interception, working certificate validation and no separate VPN or other encrypted tunnel. “Page content” includes the URL path and query parameters, request headers, cookies, submitted data and the response.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Connection to proxy&lt;/th&gt;
&lt;th&gt;Destination website&lt;/th&gt;
&lt;th&gt;Can the proxy read page content?&lt;/th&gt;
&lt;th&gt;Can someone observing the network between you and the proxy read page content?&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;HTTP&lt;/td&gt;
&lt;td&gt;HTTP&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;HTTP&lt;/td&gt;
&lt;td&gt;HTTPS&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;HTTPS&lt;/td&gt;
&lt;td&gt;HTTP&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;HTTPS&lt;/td&gt;
&lt;td&gt;HTTPS&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;An HTTPS proxy therefore adds useful protection on the way to the proxy, but it does not turn an HTTP destination into an HTTPS website. The proxy still reads that HTTP request and sends it onward without HTTPS protection.&lt;/p&gt;

&lt;p&gt;Even with HTTPS at both stages, the proxy operator sees the source IP of your connection, the destination requested in CONNECT, and traffic volume and timing. HTTPS hides the page contents from a forwarding proxy; it does not hide the fact that you used it. The website receives the connection from the proxy's exit IP, but can still recognise your account or cookies.&lt;/p&gt;

&lt;p&gt;Proxy credentials need separate attention. With &lt;strong&gt;Basic authentication over a plain HTTP proxy connection&lt;/strong&gt;, the proxy username and password are encoded, not encrypted. An observer on that connection can recover them even when the destination website uses HTTPS: proxy authentication happens outside the website's protected connection. TLS to the proxy protects this exchange and the CONNECT request. It does not make unrelated traffic, such as separate DNS requests, private.&lt;/p&gt;

&lt;p&gt;HTTPS inspection changes the arrangement. If your application trusts a certificate authority controlled by an inspecting proxy, that proxy can establish separate TLS connections and read the traffic between them. This is used in managed networks and debugging tools. Ordinary CONNECT forwarding does not require installing a proxy's root certificate; disabling certificate checks is not a routine fix for connection problems.&lt;/p&gt;

&lt;h2&gt;
  
  
  Entering the right proxy settings
&lt;/h2&gt;

&lt;p&gt;Use the proxy hostname or IP, port, protocol and authentication details supplied for the endpoint. &lt;strong&gt;The protocol in the proxy address describes how to connect to the proxy.&lt;/strong&gt; The protocol in the website address describes the destination.&lt;/p&gt;

&lt;p&gt;For example, this curl command requests an HTTPS page through a plain HTTP proxy:&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;--proxy&lt;/span&gt; http://proxy.example:8080 https://example.com/
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;proxy.example&lt;/code&gt; and port &lt;code&gt;8080&lt;/code&gt; are placeholders to replace with your actual endpoint. The first &lt;code&gt;http://&lt;/code&gt; is intentional: curl connects to that proxy using HTTP, then uses CONNECT and TLS to reach the HTTPS website. Add the service's required authentication separately. In a graphical application, use its proxy username and password fields or the provider's permitted source-IP setting, as applicable.&lt;/p&gt;

&lt;p&gt;Use &lt;code&gt;https://&lt;/code&gt; in the proxy address only for an endpoint that accepts TLS. Changing the prefix does not enable encryption on an HTTP-only endpoint. Copy the issued hostname when the provider specifies one for HTTPS access: substituting an IP address can cause a certificate name mismatch.&lt;/p&gt;

&lt;p&gt;Interface labels can also mislead. A field called “HTTPS proxy” or “Secure proxy” may mean “the proxy to use for HTTPS websites.” It does not, by itself, prove that the application will encrypt its connection to the proxy. The endpoint scheme and the application's support determine that. Ports such as &lt;code&gt;8080&lt;/code&gt; or &lt;code&gt;443&lt;/code&gt; are conventions, not proof of a protocol.&lt;/p&gt;

&lt;h2&gt;
  
  
  Which traffic this setup covers
&lt;/h2&gt;

&lt;p&gt;A browser or HTTP client's proxy setting covers the requests that application sends through it. It does not automatically route other programs or the whole computer through the proxy. Bypass rules can also send selected destinations directly. When checking the result, use the same application and configuration that will run the actual task.&lt;/p&gt;

&lt;p&gt;An HTTP/1.1 CONNECT tunnel can carry an HTTPS session using HTTP/2 between the application and the website. The HTTP version used to talk to the proxy does not set the version inside that tunnel. HTTP/2 support on an HTTPS proxy's own connection is a separate capability.&lt;/p&gt;

&lt;p&gt;CONNECT opens a TCP tunnel. It can carry protocols other than web traffic when the application and proxy allow it, but the provider can restrict destination ports. Ordinary CONNECT does not carry UDP. UDP proxying through HTTP requires a separate mechanism, such as CONNECT-UDP, supported at both ends. An “HTTPS supported” label does not establish UDP or HTTP/3 support.&lt;/p&gt;

&lt;h2&gt;
  
  
  When a connection fails
&lt;/h2&gt;

&lt;p&gt;Identify which stage failed before replacing the proxy or changing protocols. A refusal from the proxy and a refusal from the website call for different fixes.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Symptom&lt;/th&gt;
&lt;th&gt;What to check first&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;407 Proxy Authentication Required&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Proxy credentials and the authentication method accepted by the endpoint. This is a proxy login problem, not the website's login.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;HTTP pages load, but HTTPS connections fail&lt;/td&gt;
&lt;td&gt;CONNECT support, the permitted destination port, and which proxy setting the application uses for HTTPS requests.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;A TLS error appears immediately after changing the proxy address to &lt;code&gt;https://&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;Whether that proxy port actually accepts TLS, then the proxy's certificate and hostname.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;A certificate error appears after the tunnel opens&lt;/td&gt;
&lt;td&gt;The website certificate and any HTTPS inspection affecting the connection. Keep certificate validation enabled.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;The website returns a login page, CAPTCHA or access denial after TLS succeeds&lt;/td&gt;
&lt;td&gt;The request has reached the destination. Review the site's response, account state and request behaviour; successful proxy transport does not guarantee access.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;For browsing, scraping and API requests, HTTP proxy access with CONNECT supplies the route to HTTPS destinations. Choose a TLS-protected HTTPS proxy endpoint when you also need to protect the connection to the proxy, including its authentication and tunnel requests. That additional protection is the practical reason to distinguish the two.&lt;/p&gt;

&lt;p&gt;Originally published in &lt;a href="https://proxydata.io/knowledge/http-and-https-proxies" rel="noopener noreferrer"&gt;ProxyData’s guide to HTTP and HTTPS proxies&lt;/a&gt;. This adaptation was prepared with AI assistance.&lt;/p&gt;

</description>
      <category>proxy</category>
      <category>networking</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Same proxy IP, lost login: which session expired?</title>
      <dc:creator>Alex</dc:creator>
      <pubDate>Fri, 09 Oct 2026 07:23:44 +0000</pubDate>
      <link>https://dev.to/proxydata/same-proxy-ip-lost-login-which-session-expired-2o0n</link>
      <guid>https://dev.to/proxydata/same-proxy-ip-lost-login-which-session-expired-2o0n</guid>
      <description>&lt;p&gt;A browser automation job can keep the same proxy exit IP and still lose its login. Before changing the proxy settings, separate two kinds of state: the exit assignment managed by the proxy service and the website session maintained by your client.&lt;/p&gt;

&lt;h2&gt;
  
  
  Two sessions with different jobs
&lt;/h2&gt;

&lt;p&gt;A sticky proxy session asks the provider to keep an exit assignment for a task. A common implementation uses a session label in the proxy settings, although some services use a sticky port or a dashboard option. Use the format documented for that product; adding a parameter to the destination website URL does not configure the proxy.&lt;/p&gt;

&lt;p&gt;The website session usually depends on cookies or authentication tokens. Keeping an IP does not store those values, send them on subsequent requests, or extend the website login. A client object named “session” may retain cookies and reuse connections, but its name does not enable sticky mode at the proxy provider.&lt;/p&gt;

&lt;p&gt;For independent users, keep client state isolated as well as choosing the intended proxy assignment. Separate browser profiles or separate cookie stores solve a different problem from separate proxy session labels.&lt;/p&gt;

&lt;h2&gt;
  
  
  Diagnose the symptom before changing the timer
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;What you observe&lt;/th&gt;
&lt;th&gt;What to investigate&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;The exit IP stays the same, but the website asks you to sign in again&lt;/td&gt;
&lt;td&gt;Whether the client retained and sent the required cookies or tokens, and whether the website session expired.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;The session label stays the same, but the exit changes after a pause&lt;/td&gt;
&lt;td&gt;The provider’s idle timeout, maximum lifetime, exit availability, and whether routing settings changed.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Repeated requests show one IP on a single TCP connection&lt;/td&gt;
&lt;td&gt;Whether the same assignment also survives new proxy connections. One reused connection alone does not establish sticky behavior.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;These observations narrow the investigation; they do not prove a single cause. A valid website session may survive an IP change if the website permits it. Conversely, a stable IP cannot prevent logout caused by an expired session or missing cookie.&lt;/p&gt;

&lt;h2&gt;
  
  
  Test both kinds of continuity
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Open several new proxy connections using the same supported session label and routing settings. Record the exit address and time.&lt;/li&gt;
&lt;li&gt;Reproduce the pauses in the real job. Check both the provider’s maximum lifetime and its idle timeout.&lt;/li&gt;
&lt;li&gt;Run the complete application workflow with its actual cookie or token storage. Confirm that the required state survives between steps.&lt;/li&gt;
&lt;li&gt;If an interruption happens after a request that changes data, check whether the original action completed before repeating it.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Changing the proxy TTL cannot restore a missing cookie or an expired website login. Treat the proxy assignment and the website session as separate parts of the test.&lt;/p&gt;

&lt;p&gt;Based on &lt;a href="https://proxydata.io/knowledge/sticky-sessions" rel="noopener noreferrer"&gt;ProxyData’s Sticky Sessions guide&lt;/a&gt;. This technical note was prepared with AI assistance.&lt;/p&gt;

</description>
      <category>proxy</category>
      <category>networking</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
