using a proxy i receive: resolving host in proxy script... it's very slowing
Reported by
mbr...@gmail.com,
Sep 22 2016
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36 Example URL: www.repubblicait Steps to reproduce the problem: 1. open a new tab 2. visit www.repubblica.it 3. What is the expected behavior? no delay What went wrong? i got a lot of delay Did this work before? Yes on previous OS, el capitan same chrome Chrome version: 53.0.2785.116 Channel: stable OS Version: OS X 10.12.0 Flash Version: Shockwave Flash 23.0 r0 Effective proxy settings PAC script: http://inet-conf.gtm.corp.sanpaoloimi.com/files/inetdir.pac Source: SYSTEM
,
Sep 23 2016
Hi, partially resolved. it's not a chrome bug it's a Mac OSX sierra bug. Change settings from automatic proxy configuration via PAC files to fixed web proxy, it works.
,
Sep 23 2016
Going to go ahead and WontFix. If you determine Chrome really is doing something wrong, feel free to file a new bug.
,
Sep 23 2016
I can't access the proxy script (internal network I presume), however the issue is going to be that it is doing some sort of DNS looukup (i.e. dnsResolve() or dnsResolveEx(), isInNet() etc), and those lookups are slow. If the PAC script doesn't need to resolve DNS then it will avoid blocking at that part. (When you change the settings to use a fixed web proxy it avoids doing any client-side DNS lookup for your target URL.)
,
Sep 24 2016
I open a case to apple. You can close it.
,
Sep 26 2016
I am fine closing this bug, but I don't think Apple is going to be able to fix this... The interpretation of the PAC script is being done by Chrome not Mac OS; and to a large extent the speed of the PAC script depends on how the network admin wrote it, as well as speed of DNS resolution in your network. |
||
►
Sign in to add a comment |
||
Comment 1 by mbr...@gmail.com
, Sep 22 2016