8

Easy one to miss if you run a lot of pages in one automated Chrome behind a proxy: Chrome allows 32 simultaneous connections through an HTTP/1.1 proxy. Past that, requests wait inside the browser before the proxy ever sees them.

So throughput sits flat no matter how many tabs you add, and it's tempting to blame the proxy and go looking for a bigger plan. That won't help. Splitting the work over several browsers will.

Two more Chrome oddities in the same area. A user:pass@ URL in --proxy-server fails with net::ERR_NO_SUPPORTED_PROXIES, because Chrome doesn't use credentials embedded in proxy settings. And a password-protected SOCKS5 server doesn't work at all, since Chrome supports no SOCKS5 auth methods, so you get net::ERR_SOCKS_CONNECTION_FAILED whatever your code does.

no comments (yet)
sorted by: hot top new old
there doesn't seem to be anything here
this post was submitted on 04 Nov 2026
8 points (72.2% liked)

Programming

29306 readers
493 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 3 years ago
MODERATORS