Comment 6 for bug 1691462

Revision history for this message
Daniel Murray (d-daniel-t) wrote :

This happened for me when I had https_proxy etc set with a https protocol (e.g. set to https://localhost:3128) instead of just http.