You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're currently seeing over 12/Gb of bandwidth usage per hour over our proxy provider, which they are of course delighted to bill us for. We've tracked down a large percentage of the bandwidth to to URLs in the code below, which appears to be between Chrome/Chromedriver and Google servers, especially gvt1.com
Is there any way to disable Chrome's need to check for updates, or whatever it's doing, every single time it loads?
Alternatively, what's wrong with our code that is preventing the proxy bypass code from working?
With this code, we're still seeing traffic to and from: gvt1.com & googleapis.com over the socks5 proxy, so it's not bypassing correctly.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We're currently seeing over 12/Gb of bandwidth usage per hour over our proxy provider, which they are of course delighted to bill us for. We've tracked down a large percentage of the bandwidth to to URLs in the code below, which appears to be between Chrome/Chromedriver and Google servers, especially gvt1.com
Is there any way to disable Chrome's need to check for updates, or whatever it's doing, every single time it loads?
Alternatively, what's wrong with our code that is preventing the proxy bypass code from working?
With this code, we're still seeing traffic to and from: gvt1.com & googleapis.com over the socks5 proxy, so it's not bypassing correctly.
Suggestions?
Beta Was this translation helpful? Give feedback.
All reactions