Huge incompatibility with Divi #430
Description
This plugin's 'sanitize_file_name' filter totally screws up the file-based caching that Divi and the plugins Bloom and Monarch do. When the Divi theme, for example, serializes the minified CSS for a page or for the site's global styling, or when it serializes the content of a page into a binary ".data" file for caching, it constructs a potential file name for this content using a particular structure for this file name. It then does a glob of the potential target directory to see if there already is an existing file that can be used (previously cached). However, when Divi constructs this potential file name, it passes it through the sanitize_file_name function (see the constructor of the ET_Core_PageResource class in Divi/core/components/PageResource.php), which applies the 'sanitize_file_name' filter.
This means that wp-stateless prepsends this potential file name with a random string, so in the call to glob no matching files are found. This means that, on every single request for that page, Divi will write the serialized data to disk after globbing for an existing cached file!
This behavior quickly used up all 20 GB of the disk where these files were being written, and it noticeably hurt performance of my websites.
I'm running the version 2.3.2 of this plugin in stateless mode. Please address this as soon as possible.
