Closed GoogleCodeExporter closed 8 years ago
Hi
Thanks for reporting the issue. I'll be happy to incorporate the fix.
Could you please help me verify couple of things?
1) Let's simplify the config. Try this:
<system.net>
<defaultProxy useDefaultCredentials="true"/>
</system.net>
According to MSDN, nested <proxy> element should ONLY be used when I need to
change settings, and usesystemdefault="True" works as compatibility layer for
1.1 apps.
2) What happens if you set this configuration but you DO NOT have stored
credentials or ther are INCORRECT?
Original comment by agentmc@mail.ru
on 14 Jul 2014 at 8:02
1) Looks good.
2) Then the error should come up because you will not be able to browse the
internet.
If you don't have stored credentials, then it means you don't use credentials
(no proxy) and you should have direct connection to the web.
I took my nested proxy out of my config file and will let you know if this does
NOT resolve it. But so far it is looking OK ;-)
Original comment by duppi...@gmail.com
on 15 Jul 2014 at 3:36
1) Great, thanks.
2) Well, actually I expect no errors, because:
a) There're global try-catches around Auto-Updater thread and GoogleAnalytics engine;
b) The dialog for credentials should probably pop up.
So, for (2) what interests me is: when you clear stored credentials, start
Power8 and select "enable auto-updates" - what happens:
a) there is a system dialog prompting for credentials;
b) nothing happens, there probably are exceptions internally, and there's a
warning sign on Power8 button in 12 hours "unable to check updates";
c) Power8 shows error message and crashes.
I'll really appreciate if you can check the case (2).
Original comment by agentmc@mail.ru
on 15 Jul 2014 at 5:33
Sorry, I am trying to help you but our IE settings are controlled by a group
policy.
So I cannot get my credentials deleted really because it does a domain logon.
Original comment by duppi...@gmail.com
on 15 Jul 2014 at 5:57
Ok, thank you for trying :)
I'll just check in it as is, and when I have spare time will try to run
something like burpsuit or so... and hope it works then.
Guess, the fix could be really tested only after the next release, so for now
putting it to Started/Fixed.
Original comment by agentmc@mail.ru
on 15 Jul 2014 at 7:22
This issue was closed by revision r802.
Original comment by agentmc@mail.ru
on 15 Jul 2014 at 7:23
Original issue reported on code.google.com by
duppi...@gmail.com
on 14 Jul 2014 at 8:07