Comment #19 on issue 2764 by [email protected]: Implement custom PAC
support leveraging V8
http://code.google.com/p/chromium/issues/detail?id=2764
@ejohnson0547:
Can you describe in more detail your setup, and what is not working?
I just verified that this works for me in Chrome 2.0.173.1.
Try double checking the flags being passed to chrome (in case one of those
is
overriding the settings), and the particular version of chrome you are
using by
navigating to "about:version" (note that after updating you need to restart
chrome
for that update to take root).
Failing the above, you can try running Chrome with these additional flags:
--enable-logging --log-level=0
Now add an "alert('reached');" in FindProxyForURL(). If it is in fact
getting
reached, there will be a trace line showing up in chrome_debug.log.
chrome_debug.log is in the same directory as the chrome binary, something
along the
lines of C:\Documents and Settings\your_user_name\Local Settings\Application
Data\Google\Chrome\Application\chrome_debug.log
--
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
-~----------~----~----~----~------~----~------~--~---
