HTTP Reviews

Bright Data Reviews

1. Sam Mitchell

   · Owner at KittenProperties · over 2 years ago
   Mixed feelings

   We used their DC proxies and Residential proxies. Resi proxies were having quite low success rate. We had to use resi solution from other proxy providers. Unblocker didn't work well either also it was way too expensive.

   Competitors: Decodo, NetNut.io

   Pros:    Cheap dc proxies

   Cons:    Quite expensive|Residential proxies are worse than competitiors

HTTP mentions (9)

• The History of HTTP

  HTTP/1.1 was first published as RFC 2068 (The Proposed Standard) in January 1997. HTTP/1.1 protocol was refined over two revisions, RFC 2616 published in June 1999 and RFC 7230-RFC 7235 published in June 2014 before the release of HTTP/2. The HTTP/1.1 standard (RFC 2616) remained stable for over 15 years. In 2022, HTTP/1.1 was updated again with RFC 9110 & RFC 9112. - Source: dev.to / 11 months ago

• State management in Svelte apps

  HTTP was invented as a stateless protocol, which means that each request fully encapsulates all of the information necessary to return a correct response. So historically, web pages never had to worry about managing state - each request to a URL with parameters or with a form submission would receive a response with all of the HTML that the browser needed to render content. - Source: dev.to / about 2 years ago

• Evolving the Web: Discovering the History of HTTP Versions

  HTTP/1.1 was such a game changer for the Internet that it works so well that even through two revisions, RFC 2616 published in June 1999 and RFC 7230– RFC 7235 published in June 2014, HTTP/1.1 was extremely stable until the release of HTTP/2.0 in 2014 — Nearly 18 years later. Before continuing to the next section about HTTP/2.0, let us revisit what journey HTTP/1.1 has been through. - Source: dev.to / about 3 years ago

• Poll: Are client web requests sent to upstream servers or downstream servers?

  On the one hand, it just seems natural that "upstream" refers to the inbound request being sent from one system to another. It takes effort (connection pooling, throttling, retries, etc.) to make a request to an (upstream) dependency, just as it takes effort to swim upstream. The response is (usually) easy... Just return it... hence, "downstream". Recall the usual meaning of "upload" and "download". Upstream seems... - Source: Hacker News / over 4 years ago

• How to cache TCP, SSL handshake on ALB?

  To me it sounds like you’ve not solved this as the config you’ve mentioned is about preventing “illegal” (none RFC7230 ) requests, it isn’t really related to the problem you posted. Source: over 4 years ago

Bright Data mentions (45)

• Precursor

  Happy to offer a counter of some great products for anti-bot defeat: https://brightdata.com/ https://www.zenrows.com/ https://www.capsolver.com/ https://scrapfly.io/ hundreds of millions of residential ips, human browser fingerprints, custom browser binaries, auto solve of turnstyle, recaptcha v3, kasada, datadome, AWS WAF, etc if they come up. - Source: Hacker News / about 2 months ago

• Best Web Scraping Tools in 2026: A Hands-On Comparison of the Top 10

  The best web scraping tools 2026 leaderboard hasn't changed; the gap has narrowed. Bright Data remains the safest bet for any team that wants to spend time on the data, not on the scraping. The 660-scraper library, 400M-IP network, pay-per-success pricing and unlimited concurrency are still uncontested at the high end. - Source: dev.to / 4 months ago

• The Economics of Web Scraping: How Consultancies Price Data Extraction and Manage Scope Creep

  Infrastructure Pass-Through (OpEx) Data extraction at scale is infrastructure-heavy. Bypassing modern Web Application Firewalls (WAFs) requires high-quality residential proxies, CAPTCHA solvers, and substantial browser-automation compute resources. Services like Bright Data charge significantly by the gigabyte for premium residential IPs. These variable infrastructure costs must be passed directly to the client,... - Source: dev.to / 4 months ago

• LinkedIn Scraping Is Dead: 5 Legal, ToS-Safe Alternatives That Actually Work in 2026

  Bright Data has successfully defended web scraping in U.S. Courts and offers LinkedIn datasets pre-collected and ready to download. LinkedIn profile data on their dataset marketplace runs around $250 per 100,000 records. The freshness caveat is real: bulk datasets are snapshots, not real-time. If you need current job titles on a rolling basis, you're better with an enrichment API than a one-time dataset pull.... - Source: dev.to / 5 months ago

• Building a Live AI Market Research Terminal: How Bright Data and Convex Replace Polling With Real-Time Everything

  Bright Data built an open-source demo that solves this. It's called the Signal Terminal, a financial research tool built around that problem. - Source: dev.to / 6 months ago