Please enable / Bitte aktiviere JavaScript!
Veuillez activer / Por favor activa el Javascript![ ? ]
How to configure proxy in Google Chrome ? - Q&A

How to configure proxy in Google Chrome ?

0 like 0 dislike
The history of the problem — Chrome started to slow down. (Chrome 17.0.963.12 dev, WinXP sp3, no proxy, PPPoE through a router)

Symptoms — after you set the URL in the address bar and pressing "Enter" the query goes, and goes 5-70 seconds until the screen starts something to appear. And uploading is quite fast, but the access resources page can also get stuck for a few seconds.

The story of an unsuccessful solution to the problem:
1. Thought with the channel problem, but no, FireFox immediately "flies".
2. I thought the plug-in or extension may be to blame. Disabled all plugins (chrome://plugins/) and extensions (chrome://extensions/). Checked is enabled (chrome://flags/) — all disabled.
3. Decided that problems with the cache or garbage. Cleaning the cache, and other data using CCleaner — did not help.
4. To write web that may have broken the user profile. Update (delete) the user profile did not help.
5. Decided that he has broken Chrome — Uninstall Chrome full sweep of the directory
Reinstallation from scratch (took for a test version from Yandex) — did not help.
6. I realized that it wasn't Chrome, but how it tries to load the page. It was suspected that the Chrome hangs at the stage of DNS requests. Played around with DNS didn't help.

Found the option to run the tests (chrome://net-internals/#tests) is why only the 7th paragraph?

And saw such a situation (further extract from table test requests to a URL with different settings and time of access, URL of the test
  • Don't use any proxy6919 ms
  • Use system proxy settings — 183 ms
  • Use Firefox''s proxy settings — 403 ms
  • Auto-detect proxy settings - 2269 ms
  • Don't use any proxy (Disable IPv6 host resolving) — 43 ms
  • Use system proxy settings (no IPv6) — 44 ms
  • Use Firefox''s proxy settings (no IPv6) — 42 ms
  • Auto-detect proxy settings (no IPv6) — 9608 ms
  • Don't use any proxy (no IPv6) — 42753 ms
  • Use system proxy settings Probe for IPv6 host resolving — 69 ms
  • Use Firefox''s proxy settings Probe for IPv6 host resolving — 64 ms
  • Auto-detect proxy settings Probe for IPv6 host resolving — 2291 ms

From time to time the numbers are different but the trend is one and the same (highlighted in bold).

Understand that the problems with proxies. And why FireFox flies.

But! what the...

In FF proxy is disabled ("No proxy").
In Windows proxy proxycfg uplachen → Direct access (no proxy server).
In IE proxy is disabled. In the "configure network settings" all ticks removed.

To summarize.
Chrome with the setting "no proxy" is globally slow. (run with --no-proxy-server similar)
With the "automatic detection" slow but less.
Option "System proxy" and "Firefox proxy" will be considered when the ideal choice
(although both the idea is the same "no proxy").

I broke my entire head.

Why, it would seem, in three similar cases, the "no proxy" (FireFox,Chrome, system) such different results?

The question is how the mechanism "proxy" in Chrome?
And how to configure it properly?

p.s. or at least get to use "system proxy".
asked by | 10 views

2 Answers

0 like 0 dislike
Button "to Change the settings of the proxy server" in Chrome opens the standard proxy settings for IE and Windows.
And do not set any other Programul type Proxycap, which can forward the proxy on chrome?
These are often used for online games that do not have their own proxy settings.
These programs (don't know how to say) like cheating using the Internet application into thinking that it is a proxy already set up.
answered by
0 like 0 dislike
Well, firstly Fox their lives, and chrome tied to Windows, IE and so on.

Most likely the system PROXIFIER called staged once, and was demolished the usual shift+, or uninstall and not checking if he left (especially wincap love with the Windows reinstallation after.... ) or not

Well, first of all to look at all through which to connect the chrome and Fox
then have to deal with DNS not DNS, che there still

and the console
ipconfig +
/all Display full information for all adapters. /flushdns Cleaning of the DNS cache. /registerdns Updates all reserved addresses for DHCP and re-register DNS names. /displaydns display the contents of the DNS cache. /showclassid adapter Displays the DHCP class ID for a specified adapter. Only available when configured with auto obtain IP addresses. /setclassid command adapter [codes] change the code of the DHCP class. Only available when configured with auto obtain IP addresses. /? Help.
answered by
Welcome to Bug-code Q&A, where you can ask questions and receive answers from other members of the community.

24.8k questions

46.2k answers


12.7k users

24,788 questions
46,220 answers
12,724 users