logo
Breakingweb-scraping-api

Proxy mode moves to pm.scrape.do:8080

View as Markdown

Proxy mode now runs inside the Scrape.do gateway at pm.scrape.do:8080. The old address, proxy.scrape.do:8080, will be switched off on April 30, 2027, and customHeaders is now false by default.

3D illustration: your code's request passes through the pm.scrape.do gateway to the target site. Proxy mode moves to pm.scrape.do.

Proxy mode now runs inside the Scrape.do gateway, at a new address:

http://YOUR_TOKEN:PARAMETERS@pm.scrape.do:8080

It uses the same authentication, limits and logs as API mode. The old address, proxy.scrape.do:8080, keeps working until it is switched off on April 30, 2027.

What to change

  • The host. Replace proxy.scrape.do with pm.scrape.do. Your token, parameters and port stay the same.
  • Your own headers and cookies, if you send them. customHeaders is now false by default, so Scrape.do generates the request headers. To forward your own headers and cookies to the target, add customHeaders=true to the password: http://YOUR_TOKEN:customHeaders=true@pm.scrape.do:8080. Browser automation through proxy mode (Playwright, Puppeteer, Selenium) usually needs it, so the browser's own cookies and user agent reach the website.
  • Nothing else. The Scrape.do CA certificate is the same, so there is nothing to reinstall, and every parameter costs what it did.

One error looks different

A wrong or inactive token on an HTTPS target now fails while the connection is set up, with 407 Proxy Authentication Required (curl: CONNECT tunnel failed, response 407). If you see it, check your token.

The Proxy Mode documentation has the details and examples in eight languages.

On this page