{"action":"opened","issue":{"url":"https://api.github.com/repos/websharks/comet-cache/issues/757","repository_url":"https://api.github.com/repos/websharks/comet-cache","labels_url":"https://api.github.com/repos/websharks/comet-cache/issues/757/labels{/name}","comments_url":"https://api.github.com/repos/websharks/comet-cache/issues/757/comments","events_url":"https://api.github.com/repos/websharks/comet-cache/issues/757/events","html_url":"https://github.com/websharks/comet-cache/issues/757","id":152862168,"number":757,"title":"iThemes conflict(?) causing random 500 errors on Chrome","user":{"login":"MarioKnight","id":11354784,"avatar_url":"https://avatars.githubusercontent.com/u/11354784?v=3","gravatar_id":"","url":"https://api.github.com/users/MarioKnight","html_url":"https://github.com/MarioKnight","followers_url":"https://api.github.com/users/MarioKnight/followers","following_url":"https://api.github.com/users/MarioKnight/following{/other_user}","gists_url":"https://api.github.com/users/MarioKnight/gists{/gist_id}","starred_url":"https://api.github.com/users/MarioKnight/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/MarioKnight/subscriptions","organizations_url":"https://api.github.com/users/MarioKnight/orgs","repos_url":"https://api.github.com/users/MarioKnight/repos","events_url":"https://api.github.com/users/MarioKnight/events{/privacy}","received_events_url":"https://api.github.com/users/MarioKnight/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-05-03T20:04:34Z","updated_at":"2016-05-03T20:04:34Z","closed_at":null,"body":"Over the past couple of weeks, I have been getting reports of different people getting random 500 errors on a couple of sites.  At the time, I believe it to just be Chrome, and even put in a ticket at https://bugs.chromium.org/p/chromium/issues/detail?id=607572 about it.  In attempts to troubleshoot what I could on my end, I have been able to determine that there is something with the combination of Comet Cache (Pro?) and iThemes Security causing this.\r\n\r\nI have kept the non-working tab open to properly test.  When deactivating iThemes on a different machine and refreshing the non-working tab on my laptop, the page loads with no issues.  Reactivating the plugin and refreshing on my laptop, the 500 error returns.  I have had colleagues and clients come to me before I got this confirmed, and I see the common links between the sites are that they run up to date WordPress installs with up to date active iThemes Security and active Comet Cache Pro.  After doing the above, I also deactivated Comet Cache Pro, got the site back, but on re-activation, the site did not return to 500.\r\n\r\nIn searching for any sort of potential previous reports of the issue, I came across this thread - https://wordpress.org/support/topic/ithemes-security-throwing-semi-random-internal-server-500-error?replies=13 - with no real resolution, despite a fair amount of research and information.  Continuing on from that thread, these sites have not had the file change detection function active at any point.  The .htaccess files of all contain the stock WordPress code, the iThemes add-ons, GZIP compression, and some basic redirect rules.\r\n\r\nFor server logs, the apache error logs for the reported sites only show blocks as such:\r\n\r\n```\r\n[Tue May 03 13:04:32 2016] [error] [client 162.158.126.23] Premature end of script headers: index.php\r\n[Tue May 03 13:13:19 2016] [error] [client 162.158.126.23] Premature end of script headers: index.php\r\n[Tue May 03 13:13:49 2016] [error] [client 162.158.126.23] Premature end of script headers: index.php\r\n[Tue May 03 13:14:04 2016] [error] [client 162.158.126.23] Premature end of script headers: index.php\r\n```\r\n\r\nThe access logs also don't really show detail:\r\n\r\n```\r\n162.158.126.23 - - [03/May/2016:13:13:18 -0400] \"GET / HTTP/1.1\" 500 632\r\n162.158.126.23 - - [03/May/2016:13:13:47 -0400] \"GET / HTTP/1.1\" 500 632\r\n```\r\n\r\nI'm not sure what else I can really check at this point.  The logs sadly did not give much information.  It seems that something is happening with the combination of the two plugins but I don't really have the know-how to put together the final pieces in this.  Any assistance would be greatly appreciated (though now that my confirmed unworking tab is working, I don't know how well I can test), and if there's anything i can do on my end to help further, please let me know."}}