CodeClimber

In this post I’ll show something that I just discovered and solved a problem I had once we introduced a in-house git repository: how to have many git repositories using proxies but have one that connects directly without proxy. Lately we moved our source code repository, from a “standard” TFS repo to the git-based TFS repository that has been introduced with TFS 2013. Besides working with github repositories, now I had to connect also to some a repository hosted inside the local network and authenticate using the local domain credentials. All went well from within Visual Studio, but...

Lately the proxy configuration of my network has been changed, and moved from a transparent proxy, that required no configuration, to a “standard” proxy which requires a configuration script. Unfortunately NPM doesn’t pick up the proxy configuration of Windows, and it took me a while to understand how to download node packages via NPM, so sharing here. Basically you just run config set option of npm to set the proxy and https-proxy config keys, like this: npm config set proxy http://proxy.example.com:8080 npm config set https-proxy http://proxy.example.com:8443 ...

[UPDATE: There is a workaround] This morning, following the release of Chrome 6, I decided to upgrade to the latest version. But as soon as I tried going to Gmail I got the following error: SSL connection error. Unable to make a secure connection to the server. This may be a problem with the server, or it may be requiring a client authentication certificate that you don't have. Error 128 (net::ERR_SSL_UNSAFE_NEGOTIATION): The SSL renegotiation extension was missing from the secure handshake. For some sites, which are known to support the renegotiation...