GitLab

Using the bleedingest edge version of https-everywhere from git master, if you were to go to something like news.google.com, and it were to then load clients1.google.com/ocsp, it will POST some ocsp crap, but then it might continue to do so for a variable amount of time until it has it's fill or until you play a fun game of close-the-connections-manually in vidalia. Removing clients1 from GoogleServices.xml seems to prevent this from happening, but that sort of defeats the whole purpose of https-everywhere...