hsple.blogg.se - Google chrome settings crash

91 stable for Windows and got the same result. Tested uMatrix of the lastest version on Chrome 64Bit. When a browser crashes, it means there is a bug in the browser, and this needs to be reported to the browser devs. HTTP Switchboard is javascript: javascript doesn't crash. HTTP Switchboard is no longer maintained, it is superseded by uMatrix. Is it compatible with SSL client auth? Reply from gorhill No matter HTTPswithcboard is disabled or not,all works fine without issue,no crash. Two way SSL authentication is turn off and authentication is based on Basic-Auth. If proxy settings is on and HTTPswithcboard is disabled,Chrome is able to work as usual and access the Internet through proxy after starting up with no crash.If proxy settings is on,and an issue is made that I disable the cleint cert, as mentioned above and I enable the client cert after Chrome starts without crashes as expected,Chrome is still able to work well beyond my expectation.It can access the Internet via proxy with authentication of client certificate.

If proxy settings is on,but there is any issue that causes failure of client authentication,Chrome doesn't crash.For example,it is able to start when server cert or client cert is untrusted.

If proxy settings is on,Chrome crashes with a prompt windows from system asking me whether to >let Chrome restart as soon as it is started and it doesn't generate any report which could be found in chrome://crashes.

It doesn't matter Chrome is set with arguement `-proxy-server' or with SwithcSharp,Chrome crashes >as been expected.

Two way SSL authentication is turn on and all settings on both server and client,my conputer > seem correct. Igrigorik/node-spdyproxy is running on my server.