Updates:
Status: Fixed
Comment #26 on issue 6567 by w...@chromium.org: URL's fail to load if behind
a proxy in 2.0.157.2
http://code.google.com/p/chromium/issues/detail?id=6567
Thanks to all who tested the latest nightly build and posted their
test reports.
Re: the need to enter username/password (domain credentials) for
NTLM authentication: the lack of automatic logon for NTLM auth is
a known issue of Chromium (issue 19). The stable channel release
of Google Chrome 1.0.154.x has the same issue. This bug is only
concerned with the regression that NTLM did not work at all.
Re: igitur's comment 23: I'll try to find out more about Privoxy.
I'd appreciate it if you could test a stable channel release of
Google Chrome (version 1.0.154.x) and Firefox 3.0.x against Privoxy.
Since we copied Firefox's NTLM code, our behavior should be the
same as Firefox with these preference settings:
- network.automatic-ntlm-auth.allow-proxies: false
- network.automatic-ntlm-auth.trusted-uris: (empty string)
- network.ntlm.send-lm-response: false
You can examine and set these Firefox preferences by typing
"about:config" into Firefox's location bar and then typing "ntlm"
into the Filter field.
--
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
-~----------~----~----~----~------~----~------~--~---
