The changes made to add 'http' vs. 'https' support appear to have resulted in breaking this plugin pretty badly. Files aren't being deleted any more when comments are posted so most users are getting stale content.
IMO, this is indicative of a more serious problem that is only going to propagate itself and you need to nip it in the bud right now before it gets a lot worse and this plugin becomes severely unwieldy to manage. Creating lots of directory entries based on metadata of the request is the wrong approach. When someone goes to post a comment, how are you going to know which files to remove from the cache? You can't if you are using metadata in the paths. Adding 'http' and 'https' to the paths was a bad move. Put ALL files for the same cache entry in the same directory so you can simply do an opendir()/readdir()/unlink()/closedir() on all files in the current cache directory and know that you successfully wiped all relevant files. A better approach would be to do:
Or something similar if you really need to differentiate the protocol used. It will simplify your rewrite rules too. And it also starts you down the right path of better supporting mobile themes.