Status: Unconfirmed
Owner: ----
Labels: Type-Bug Pri-2 OS-All Area-Misc
New issue 19298 by [email protected]: Chrome should give up the first time
after getting a 407 DENIED from a proxy server, when attempting to reach
cr-tools.clients.google.com.
http://code.google.com/p/chromium/issues/detail?id=19298
Chrome Version : all tested
URLs (if applicable) : cr-tools.clients.google.com
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 4: OK
Firefox 3.x: OK
IE 7: OK
IE 8: OK
What steps will reproduce the problem?
1. Simply start chrome from behind an authenticating proxy, and wait for it
to phone home
2. Watch your proxy server being DDoS'ed as it hammers away at 10-20
requests/sec to reach cr-tools.clients.google.com, despite getting a
407-DENIED response from the proxy
What is the expected result?
Chrome should give up after the first 407-DENIED response from the proxy.
What happens instead?
Chrome hammers away at 10-20 requests/sec trying to reach
cr-tools.clients.google.com, effectively DDoS'ing the proxy and rapidly
filling up logs, despite receiving a 407-DENIED response on every request.
In the HTTP protocol, 4xx errors can generally be seen as "Permanent
Errors" - not sensible candidates to just blindly retry without
intervention.
Please provide any additional information below. Attach a screenshot if
possible.
Chrome will shortly be banned from our campus because of this.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
