In my particular case, and all of a sudden, an extra parameter on the file_get_contents URL was causing this error. I believe something in my firewall software just got smarter about injections and started throwing the error without warning. I was adding a random variable to the URL to force a requery instead of taking the cache and I believe that somehow the random variable was seen as an injection attack.