Re: Fiddler not working with Chrome

[EricLaw]

The last person to complain of this had forgotten that they had recently installed a Chrome "Proxy Switcher" extension that changed Chrome not to use the system's proxy settings. Might that be what you did?

 

If not, what happens in Chrome if you try to visit http://ipv4.fiddler:8888/ and http://localhost:8888/ ?

 

thanks,

Eric

 

On Tuesday, January 15, 2013 7:23:30 PM UTC-6, David Kaing wrote:

Fiddler2 

Hi, Since updating to Chrome v23 stable and v24 Fiddler2 hasn't been able to capture its traffic.

Fiddler2 is capturing Internet Explorer's traffic with no issues, as well as those applications that use its proxy settings - MSN Live Messenger etc.

Chrome appears to be the only exception to this.

Chromium works fine though - latest build

http://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?path=Win/176978/

Environment

Win 7 x64

Fiddler 2.4.2.4

Proxy - TMG 2010 

Wpad set via DNS

[David Kaing]

No extensions enabled. Tried on a couple different machines with this SOE (no extensions installed at all, new install).

Same result.

Going to http://localhost:8888 gives the following:

Fiddler Echo Service

GET / HTTP/1.1
Host: localhost:8888
Connection: keep-alive
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.52 Safari/537.17
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

I get - Host not found when tyring to go to http://ipv4.fiddler:8888/ 

Thanks,

[EricLaw]

This indicates that your Chrome instance is not respecting the system proxy setting. You may want to ask the Chrome team what bugs they may have in that regard.

 

What, if any, antivirus software do you have installed?

 

I'm not sure what you would like "SOE" to expand to.

[EricLaw]

I see one bug filed against Chrome with similar symptoms: http://code.google.com/p/chromium/issues/detail?id=149165 and another that's somewhat related: http://code.google.com/p/chromium/issues/detail?id=118385. 

 

You might try the steps they suggest for troubleshooting.

 

-Eric

[David Kaing]

Figured out that it was due to a group policy setting. 

If Chrome has this set via GPO - it will not tell you in chrome://net-internals/#proxy

Basic Settings page only indicate 'something' has been set.

Thanks for those links they helped.

[EricLaw]

Fascinating-- can you tell me a bit more?  Is the GPO a Chrome-specific policy, or is this the WinINET-GPO that Chrome is reading?  Thanks!

[David Kaing]

Chrome specific. User error on my behalf, but it wasn't clear to me that it was the issue.

 

GPO details:

 

Choose how to specify proxy server settings:

 

Allows you to specify the proxy server used by Google Chrome and prevents users from changing proxy settings.

If you choose to never use a proxy server and always connect directly, all other options are ignored.

If you choose to use system proxy settings or auto detect the proxy server, all other options are ignored.

If you choose fixed server proxy mode, you can specify further options in 'Address or URL of proxy server' and 'Comma-separated list of proxy bypass rules'.

If you choose to use a .pac proxy script, you must specify the URL to the script in 'URL to a proxy .pac file'.

For detailed examples, visit:
http://www.chromium.org/developers/design-documents/network-settings#TOC-Command-line-options-for-proxy-sett

If you enable this setting, Google Chrome ignores all proxy-related options specified from the command line.

Leaving this policy not set will allow the users to choose the proxy settings on their own.

[EricLaw]

Awesome, thanks for the details! I'll look into what I can do to detect this, and also put it in my troubleshooting list.